Trace number 253006

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
Abscon 109 ESACUNSAT 0.661899 0.718811

DiagnosticValue
CHECKS1126
NODES6

General information on the benchmark

Namecoloring/
geom-30a-3-ext.xml
MD5SUM988fc81fbaf808399fb7936f353f616c
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.003998
SatisfiableNO
(Un)Satisfiability was proved
Number of variables30
Number of constraints81
Maximum constraint arity2
Maximum domain size3
Number of constraints which are defined in extension81
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.31	   
0.31	Abscon 109 (November, 2006)
0.31	   
0.31	   configuration
0.31	     name=esac.xml
0.34	   
0.34	   instance
0.34	     name=/tmp/evaluation/253006-1168409719/unknown.xml
0.37	   
0.37	   domains being loaded...
0.37	   
0.37	   variables being loaded...
0.40	     nbVariables=30  nbDomainTypes=1  minDomainSize=3  maxDomainSize=3
0.40	       =>  wckTime=0.094  cpuTime=0.08  mem=6M951
0.40	   
0.40	   relations being loaded...
0.40	   
0.41	   constraints being loaded...
0.45	     nbConstraints=81  nbRelationTypes=1  nbExtensionStructures=1  nbSharedExtensionStructures=80
0.45	     nbConflictsStructures=1  nbSharedConflictsStructures=80  nbSharedBinaryRepresentations=3  maxDegree=10  maxArity=2
0.45	       =>  wckTime=0.137  cpuTime=0.12  mem=7M959
0.48	   
0.48	   solver IterativeSystematicSolver being built... 
0.64	       =>  wckTime=0.329  cpuTime=0.25  mem=14M400
0.66	   
0.66	   preprocessing
0.66	     nbConstraintChecks=842  nbPropagations=268  nbRevisions=337  nbUselessRevisions=16  nbSingletonTests=52
0.66	     nbEffectiveSingletonTests=0  nbESACBranches=22  nbRemovedValues=0  detectedInconsistency=no
0.66	       =>  wckTime=0.025  cpuTime=0.01  mem=14M400
0.67	   
0.67	   search
0.67	     run=0  nbConstraintChecks=284  nbPropagations=320  nbRevisions=475  nbUselessRevisions=52  nbAssignments=6
0.67	     nbFailedAssignments=3  nbBacktracks=4  nbVisitedNodes=12  nbRestartNogoods=0  mapSize=3  nbInferences=0
0.67	     nbTooLargeKeys=0
0.67	       =>  wckTime=0.033  cpuTime=0.02  mem=14M400
0.67	   
0.67	   global
0.67	     nbConstraintChecks=1126  nbPropagations=588  nbRevisions=812  nbUselessRevisions=68  nbRestartNogoods=0
0.67	     solvingWckTime=0.034  solvingCpuTime=0.02  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
0.67	     globalCpuTime=0.32
0.67	       =>  wckTime=0.365  cpuTime=0.27  mem=14M400
0.68	   
0.68	s UNSATISFIABLE
0.68	d NODES 6
0.68	d CHECKS 1126
0.68	   
0.68	   totalWckTime=0.439  totalCpuTime=0.32

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node26/watcher-253006-1168409719 -o ROOT/results/node26/solver-253006-1168409719 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/253006-1168409719/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 0.16 0.69 0.88 2/82 10298
/proc/meminfo: memFree=1512608/2055920 swapFree=4192812/4192956
[pid=10297] ppid=10294 vsize=1452 CPUtime=0
/proc/10297/stat : 10297 (java) R 10294 10297 9766 0 -1 0 108 0 0 0 0 0 0 0 20 0 1 0 189366403 1486848 80 18446744073709551615 134512640 134570532 4294956640 18446744073709551615 134517472 0 0 4096 0 0 0 0 17 1 0 0
/proc/10297/statm: 364 87 68 14 0 9 0

[startup+0.103099 s]
/proc/loadavg: 0.16 0.69 0.88 2/82 10298
/proc/meminfo: memFree=1512608/2055920 swapFree=4192812/4192956
[pid=10297] ppid=10294 vsize=913228 CPUtime=0.07
/proc/10297/stat : 10297 (java) S 10294 10297 9766 0 -1 0 2900 0 1 0 6 1 0 0 19 0 8 0 189366403 935145472 2646 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/10297/statm: 228307 2646 1396 14 0 215208 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 913228

[startup+0.511134 s]
/proc/loadavg: 0.16 0.69 0.88 2/82 10298
/proc/meminfo: memFree=1512608/2055920 swapFree=4192812/4192956
[pid=10297] ppid=10294 vsize=916484 CPUtime=0.47
/proc/10297/stat : 10297 (java) R 10294 10297 9766 0 -1 0 6761 0 1 0 44 3 0 0 16 0 8 0 189366403 938479616 6499 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4153604294 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/10297/statm: 229121 6499 2379 14 0 215591 0
Current children cumulated CPU time (s) 0.47
Current children cumulated vsize (KiB) 916484

Child status: 0
Real time (s): 0.718811
CPU time (s): 0.661899
CPU user time (s): 0.604908
CPU system time (s): 0.056991
CPU usage (%): 92.0825
Max. virtual memory (cumulated for all children) (KiB): 916484

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.604908
system time used= 0.056991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8516
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 435
involuntary context switches= 92

runsolver used 0.004999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node26 on Wed Jan 10 06:15:20 UTC 2007


IDJOB= 253006
IDBENCH= 12975
FILE ID= node26/253006-1168409719

PBS_JOBID= 3523382

Free space on /tmp= 66541 MiB

BENCH NAME= HOME/pub/bench/CPAI06/coloring/geom-30a-3-ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/253006-1168409719/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node26/watcher-253006-1168409719 -o ROOT/results/node26/solver-253006-1168409719 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/253006-1168409719/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  988fc81fbaf808399fb7936f353f616c

RANDOM SEED= 782414101

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.236
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.236
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1513224 kB
Buffers:         48216 kB
Cached:         376444 kB
SwapCached:          0 kB
Active:         188372 kB
Inactive:       300564 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1513224 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1992 kB
Writeback:           0 kB
Mapped:          83228 kB
Slab:            38828 kB
Committed_AS:  3795632 kB
PageTables:       2112 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66541 MiB



End job on node26 on Wed Jan 10 06:15:23 UTC 2007