Trace number 252698

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 ACUNSAT 0.671896 0.716993

DiagnosticValue
CHECKS124
NODES6

General information on the benchmark

Namecoloring/
geom-40-3-ext.xml
MD5SUMd54325db3282ef19b94f41e995b8132d
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 variables40
Number of constraints78
Maximum constraint arity2
Maximum domain size3
Number of constraints which are defined in extension78
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=mac.xml
0.35	   
0.35	   instance
0.35	     name=/tmp/evaluation/252698-1168087576/unknown.xml
0.38	   
0.38	   domains being loaded...
0.38	   
0.38	   variables being loaded...
0.42	     nbVariables=40  nbDomainTypes=1  minDomainSize=3  maxDomainSize=3
0.42	       =>  wckTime=0.1  cpuTime=0.09  mem=6M951
0.42	   
0.42	   relations being loaded...
0.42	   
0.42	   constraints being loaded...
0.46	     nbConstraints=78  nbRelationTypes=1  nbSingletonDomainVariables=1  nbDisconnectedVariables=1
0.46	     nbExtensionStructures=1  nbSharedExtensionStructures=77  nbConflictsStructures=1  nbSharedConflictsStructures=77
0.46	     nbSharedBinaryRepresentations=3  maxDegree=6  maxArity=2
0.46	       =>  wckTime=0.144  cpuTime=0.12  mem=7M992
0.49	   
0.49	   solver IterativeSystematicSolver being built... 
0.66	       =>  wckTime=0.341  cpuTime=0.26  mem=13M281
0.66	   
0.66	   preprocessing
0.66	     nbConstraintChecks=0  nbPropagations=40  nbRevisions=0  nbUselessRevisions=0  nbRemovedValues=0
0.66	     detectedInconsistency=no
0.66	       =>  wckTime=0.0010  cpuTime=0.0  mem=13M281
0.67	   
0.67	   search
0.67	     run=0  nbConstraintChecks=124  nbPropagations=76  nbRevisions=52  nbUselessRevisions=0  nbAssignments=6
0.67	     nbFailedAssignments=3  nbBacktracks=4  nbVisitedNodes=12  nbRestartNogoods=0  mapSize=3  nbInferences=0
0.67	     nbTooLargeKeys=0
0.67	       =>  wckTime=0.011  cpuTime=0.01  mem=14M256
0.67	   
0.67	   global
0.67	     nbConstraintChecks=124  nbPropagations=116  nbRevisions=52  nbUselessRevisions=0  nbRestartNogoods=0
0.67	     solvingWckTime=0.013  solvingCpuTime=0.01  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
0.67	     globalCpuTime=0.31
0.67	       =>  wckTime=0.356  cpuTime=0.27  mem=14M256
0.67	   
0.67	s UNSATISFIABLE
0.68	d NODES 6
0.68	d CHECKS 124
0.68	   
0.68	   totalWckTime=0.436  totalCpuTime=0.31

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/node35/watcher-252698-1168087576 -o ROOT/results/node35/solver-252698-1168087576 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/252698-1168087576/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
/proc/loadavg: 1.92 1.95 1.77 4/80 16083
/proc/meminfo: memFree=1543448/2055920 swapFree=4192812/4192956
[pid=16082] ppid=16080 vsize=18540 CPUtime=0
/proc/16082/stat : 16082 (runsolver) R 16080 15738 15738 0 -1 4194368 10 0 0 0 0 0 0 0 20 0 1 0 157151232 18984960 277 18446744073709551615 4194304 4267372 548682068960 18446744073709551615 266131799538 0 0 4096 24578 0 0 0 17 1 0 0
/proc/16082/statm: 4635 277 242 17 0 2626 0
Current StackSize limit: 10240 KiB


[startup+0.107295 s]
/proc/loadavg: 1.92 1.95 1.77 4/80 16083
/proc/meminfo: memFree=1543448/2055920 swapFree=4192812/4192956
[pid=16082] ppid=16080 vsize=914988 CPUtime=0.09
/proc/16082/stat : 16082 (java) R 16080 16082 15738 0 -1 0 2988 0 1 0 8 1 0 0 18 0 8 0 157151232 936947712 2734 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 2147483391 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/16082/statm: 228747 2734 1426 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.515341 s]
/proc/loadavg: 1.92 1.95 1.77 4/80 16083
/proc/meminfo: memFree=1543448/2055920 swapFree=4192812/4192956
[pid=16082] ppid=16080 vsize=915460 CPUtime=0.49
/proc/16082/stat : 16082 (java) R 16080 16082 15738 0 -1 0 6750 0 1 0 45 4 0 0 18 0 8 0 157151232 937431040 6488 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4073489092 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/16082/statm: 228865 6488 2370 14 0 215335 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915460

Child status: 0
Real time (s): 0.716993
CPU time (s): 0.671896
CPU user time (s): 0.611906
CPU system time (s): 0.05999
CPU usage (%): 93.7103
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.611906
system time used= 0.05999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8421
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= 520
involuntary context switches= 512

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node35 on Sat Jan  6 12:46:16 UTC 2007


IDJOB= 252698
IDBENCH= 12963
FILE ID= node35/252698-1168087576

PBS_JOBID= 3476529

Free space on /tmp= 66558 MiB

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

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  d54325db3282ef19b94f41e995b8132d

RANDOM SEED= 406513403

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.234
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.234
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:       1543928 kB
Buffers:         31016 kB
Cached:         358760 kB
SwapCached:          0 kB
Active:         110624 kB
Inactive:       325380 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1543928 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1648 kB
Writeback:           0 kB
Mapped:          66472 kB
Slab:            61320 kB
Committed_AS:  3928724 kB
PageTables:       1888 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= 66558 MiB



End job on node35 on Sat Jan  6 12:46:17 UTC 2007