Trace number 222269

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-wtdi 2006-12-21SAT 0.264959 0.266714

DiagnosticValue
CHECKS22876
NODES179

General information on the benchmark

Namebqwh/bqwh-15-106/
bqwh-15-106-13_ext.xml
MD5SUMbf7d9ab944270ec41210602e44c16b60
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.027994
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables106
Number of constraints644
Maximum constraint arity2
Maximum domain size6
Number of constraints which are defined in extension644
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.26	v 9 6 12 2 14 1 8 12 3 5 8 1 13 0 10 4 7 6 8 0 12 14 11 6 8 7 13 1 10 11 9 5 4 1 7 8 5 7 14 9 1 12 13 8 9 14 5 11 0 10 12 9 4 0 6 3 13 8 6 7 2 10 14 5 6 8 7 2 10 12 5 10 7 2 9 11 6 0 12 11 10 0 7 4 8 14 5 1 11 12 6 2 9 7 4 2 13 10 3 3 1 9 4 12 13 5 
0.26	c Nodes on final run 179
0.26	s SATISFIABLE
0.26	d NODES 179
0.26	d CHECKS 22876
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/node76/watcher-222269-1168264256 -o ROOT/results/node76/solver-222269-1168264256 -C 1800 -M 900 /tmp/evaluation/222269-1168264256/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.49 1.30 1.63 4/70 20569
/proc/meminfo: memFree=1851512/2055888 swapFree=4095388/4096564
[pid=20568] ppid=20566 vsize=5360 CPUtime=0
/proc/20568/stat : 20568 (solver) R 20566 20568 19554 0 -1 4194304 281 168 0 0 0 0 0 0 20 0 1 0 174823557 5488640 227 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 206843736463 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/20568/statm: 1340 227 190 169 0 50 0
[pid=20571] ppid=20568 vsize=5360 CPUtime=0
/proc/20571/stat : 20571 (solver) R 20568 20568 19554 0 -1 4194368 3 0 0 0 0 0 0 0 20 0 1 0 174823558 5488640 227 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 206843736555 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/20571/statm: 1340 227 190 169 0 50 0

[startup+0.103048 s]
/proc/loadavg: 0.49 1.30 1.63 4/70 20569
/proc/meminfo: memFree=1851512/2055888 swapFree=4095388/4096564
[pid=20568] ppid=20566 vsize=5360 CPUtime=0
/proc/20568/stat : 20568 (solver) S 20566 20568 19554 0 -1 4194304 311 168 0 0 0 0 0 0 20 0 1 0 174823557 5488640 227 18446744073709551615 4194304 4889804 548682069392 18446744073709551615 206843734596 0 65536 4100 65538 18446744071563358023 0 0 17 1 0 0
/proc/20568/statm: 1340 227 190 169 0 50 0
[pid=20571] ppid=20568 vsize=5420 CPUtime=0.09
/proc/20571/stat : 20571 (xlisp) R 20568 20568 19554 0 -1 4194304 824 0 0 0 9 0 0 0 18 0 1 0 174823558 5550080 782 18446744073709551615 134512640 135322396 4294956848 18446744073709551615 134683903 0 0 4096 130 0 0 0 17 1 0 0
/proc/20571/statm: 1355 782 244 197 0 570 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 10780

Child status: 0
Real time (s): 0.266714
CPU time (s): 0.264959
CPU user time (s): 0.255961
CPU system time (s): 0.008998
CPU usage (%): 99.342
Max. virtual memory (cumulated for all children) (KiB): 10900

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.255961
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1618
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= 40
involuntary context switches= 6

runsolver used 0.001999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Mon Jan  8 13:50:57 UTC 2007


IDJOB= 222269
IDBENCH= 5506
FILE ID= node76/222269-1168264256

PBS_JOBID= 3482652

Free space on /tmp= 66648 MiB

BENCH NAME= HOME/pub/bench/CPAI06/bqwh/bqwh-15-106/bqwh-15-106-13_ext.xml
COMMAND LINE= /tmp/evaluation/222269-1168264256/solver
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node76/convwatcher-222269-1168264256 -o ROOT/results/node76/conversion-222269-1168264256 -C 600 -M 900 /tmp/evaluation/222269-1168264256/conversion /tmp/evaluation/222269-1168264256/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-222269-1168264256 -o ROOT/results/node76/solver-222269-1168264256 -C 1800 -M 900  /tmp/evaluation/222269-1168264256/solver

META MD5SUM SOLVER= d524ecf1110edbc743abd2f199c280bf
MD5SUM BENCH=  bf7d9ab944270ec41210602e44c16b60

RANDOM SEED= 136058840

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.254
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	: 6006.17
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.254
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1851928 kB
Buffers:         44420 kB
Cached:          97408 kB
SwapCached:        428 kB
Active:          82548 kB
Inactive:        75052 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1851928 kB
SwapTotal:     4096564 kB
SwapFree:      4095388 kB
Dirty:             748 kB
Writeback:           0 kB
Mapped:          24800 kB
Slab:            32708 kB
Committed_AS:  6490564 kB
PageTables:       1424 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66648 MiB



End job on node76 on Mon Jan  8 13:51:06 UTC 2007