Trace number 205513

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
Diarmuid-rndi 2006-12-21SAT 0.555915 0.567718

DiagnosticValue
CHECKS524982
NODES30

General information on the benchmark

Namehanoi/
hanoi-5_ext.xml
MD5SUM0e5981b9a270289f8a9017b71b4850af
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.032994
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables30
Number of constraints29
Maximum constraint arity2
Maximum domain size243
Number of constraints which are defined in extension29
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.55	v 2 5 4 22 21 24 26 53 52 46 45 36 38 41 40 202 201 204 206 197 196 190 189 216 218 221 220 238 237 240 
0.55	s SATISFIABLE
0.55	d NODES 30
0.55	d CHECKS 524982
c 
c 
c 
c conversion script
c 
c

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node9/watcher-205513-1168167715 -o ROOT/results/node9/solver-205513-1168167715 -C 1800 -M 900 /tmp/evaluation/205513-1168167715/solver 

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.08 0.57 1.24 4/87 20747
/proc/meminfo: memFree=1694592/2055920 swapFree=4191880/4192956
[pid=20746] ppid=20744 vsize=5352 CPUtime=0
/proc/20746/stat : 20746 (solver) R 20744 20746 20113 0 -1 4194304 299 174 0 0 0 0 0 0 18 0 1 0 165169257 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 215418989215 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/20746/statm: 1338 229 192 169 0 49 0
[pid=20749] ppid=20746 vsize=5352 CPUtime=0
/proc/20749/stat : 20749 (solver) R 20746 20746 20113 0 -1 4194368 18 0 0 0 0 0 0 0 20 0 1 0 165169257 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 215419157093 0 2147483391 4100 65536 0 0 0 17 1 0 0
/proc/20749/statm: 1338 229 192 169 0 49 0
[pid=20750] ppid=20746 vsize=5352 CPUtime=0
/proc/20750/stat : 20750 (solver) R 20746 20746 20113 0 -1 4194368 19 0 0 0 0 0 0 0 22 0 1 0 165169257 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 215418989863 0 0 4096 0 0 0 0 17 1 0 0
/proc/20750/statm: 1338 229 192 169 0 49 0

[startup+0.10328 s]
/proc/loadavg: 0.08 0.57 1.24 4/87 20747
/proc/meminfo: memFree=1694592/2055920 swapFree=4191880/4192956
[pid=20746] ppid=20744 vsize=5352 CPUtime=0
/proc/20746/stat : 20746 (solver) S 20744 20746 20113 0 -1 4194304 313 174 0 0 0 0 0 0 18 0 1 0 165169257 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/20746/statm: 1338 229 192 169 0 49 0
[pid=20749] ppid=20746 vsize=7552 CPUtime=0.08
/proc/20749/stat : 20749 (xlisp) R 20746 20746 20113 0 -1 4194304 1409 0 0 0 8 0 0 0 18 0 1 0 165169257 7733248 1369 18446744073709551615 134512640 135322396 4294956848 18446744073709551615 134884059 0 0 4096 130 0 0 0 17 1 0 0
/proc/20749/statm: 1888 1369 241 197 0 1128 0
[pid=20750] ppid=20746 vsize=2600 CPUtime=0
/proc/20750/stat : 20750 (sed) S 20746 20746 20113 0 -1 4194304 146 0 0 0 0 0 0 0 21 0 1 0 165169257 2662400 119 18446744073709551615 4194304 4240196 548682069504 18446744073709551615 215419158610 0 0 4096 0 18446744071563648864 0 0 17 0 0 0
/proc/20750/statm: 650 119 96 11 0 54 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 15504

[startup+0.515324 s]
/proc/loadavg: 0.08 0.57 1.24 4/87 20747
/proc/meminfo: memFree=1694592/2055920 swapFree=4191880/4192956
[pid=20746] ppid=20744 vsize=5352 CPUtime=0
/proc/20746/stat : 20746 (solver) S 20744 20746 20113 0 -1 4194304 313 174 0 0 0 0 0 0 18 0 1 0 165169257 5480448 229 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 215418987332 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/20746/statm: 1338 229 192 169 0 49 0
[pid=20749] ppid=20746 vsize=16988 CPUtime=0.49
/proc/20749/stat : 20749 (xlisp) R 20746 20746 20113 0 -1 4194304 3741 0 0 0 48 1 0 0 22 0 1 0 165169257 17395712 3700 18446744073709551615 134512640 135322396 4294956848 18446744073709551615 134873622 0 0 4096 130 0 0 0 17 1 0 0
/proc/20749/statm: 4247 3700 242 197 0 3487 0
[pid=20750] ppid=20746 vsize=2600 CPUtime=0
/proc/20750/stat : 20750 (sed) S 20746 20746 20113 0 -1 4194304 146 0 0 0 0 0 0 0 21 0 1 0 165169257 2662400 119 18446744073709551615 4194304 4240196 548682069504 18446744073709551615 215419158610 0 0 4096 0 18446744071563648864 0 0 17 0 0 0
/proc/20750/statm: 650 119 96 11 0 54 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 24940

Child status: 0
Real time (s): 0.567718
CPU time (s): 0.555915
CPU user time (s): 0.529919
CPU system time (s): 0.025996
CPU usage (%): 97.9209
Max. virtual memory (cumulated for all children) (KiB): 24940

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.529919
system time used= 0.025996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4424
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 41
involuntary context switches= 21

runsolver used 0.004999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Sun Jan  7 11:02:02 UTC 2007


IDJOB= 205513
IDBENCH= 4135
FILE ID= node9/205513-1168167715

PBS_JOBID= 3478775

Free space on /tmp= 66545 MiB

BENCH NAME= HOME/pub/bench/CPAI06/hanoi/hanoi-5_ext.xml
COMMAND LINE= /tmp/evaluation/205513-1168167715/solver
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node9/convwatcher-205513-1168167715 -o ROOT/results/node9/conversion-205513-1168167715 -C 600 -M 900 /tmp/evaluation/205513-1168167715/conversion /tmp/evaluation/205513-1168167715/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-205513-1168167715 -o ROOT/results/node9/solver-205513-1168167715 -C 1800 -M 900  /tmp/evaluation/205513-1168167715/solver

META MD5SUM SOLVER= b57068d1450403a75f014042200261c5
MD5SUM BENCH=  0e5981b9a270289f8a9017b71b4850af

RANDOM SEED= 701279642

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.231
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.231
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:       1694992 kB
Buffers:         39564 kB
Cached:         211352 kB
SwapCached:        276 kB
Active:         147436 kB
Inactive:       151304 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1694992 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:             932 kB
Writeback:           0 kB
Mapped:          59956 kB
Slab:            46904 kB
Committed_AS:  4478368 kB
PageTables:       2368 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= 66545 MiB



End job on node9 on Sun Jan  7 11:02:26 UTC 2007