Trace number 204110

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
VALCSP 3.0? (MO) 6.536 6.60335

General information on the benchmark

Namedomino/
domino-3000-3000.xml
MD5SUM2856bb6534c66b8fd5677f0eaa3dd113
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.158975
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables3000
Number of constraints3000
Maximum constraint arity2
Maximum domain size3000
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3000
Global constraints used (with number of constraints)

Solver Data (download as text)



Verifier Data (download as text)




ERROR: Unexpected answer ! (SAT/UNSAT expected)
Got answer: 



Watcher Data (download as text)




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

command line: runsolver --timestamp -w ROOT/results/node17/watcher-204110-1168165295 -o ROOT/results/node17/solver-204110-1168165295 -C 1800 -M 900 /tmp/evaluation/204110-1168165295/VALCSP /tmp/evaluation/204110-1168165295/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: 1.20 1.69 1.88 5/94 14375
/proc/meminfo: memFree=1648808/2055920 swapFree=4192812/4192956
[pid=14374] ppid=14372 vsize=18540 CPUtime=0
/proc/14374/stat : 14374 (runsolver) R 14372 14374 13377 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 164924736 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 245482712359 0 0 4096 24578 0 0 0 17 1 0 0
/proc/14374/statm: 4635 279 244 17 0 2626 0

[startup+0.103107 s]
/proc/loadavg: 1.20 1.69 1.88 5/94 14375
/proc/meminfo: memFree=1648808/2055920 swapFree=4192812/4192956
[pid=14374] ppid=14372 vsize=74008 CPUtime=0.08
/proc/14374/stat : 14374 (VALCSP) R 14372 14374 13377 0 -1 4194304 17258 0 0 0 1 7 0 0 18 0 1 0 164924736 75784192 17236 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134534817 0 0 4096 0 0 0 0 17 0 0 0
/proc/14374/statm: 18502 17236 62 8 0 18174 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 74008

[startup+0.515145 s]
/proc/loadavg: 1.20 1.69 1.88 5/94 14375
/proc/meminfo: memFree=1648808/2055920 swapFree=4192812/4192956
[pid=14374] ppid=14372 vsize=318916 CPUtime=0.49
/proc/14374/stat : 14374 (VALCSP) R 14372 14374 13377 0 -1 4194304 78076 0 0 0 16 33 0 0 21 0 1 0 164924736 326569984 78054 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530198 0 0 4096 0 0 0 0 17 0 0 0
/proc/14374/statm: 79729 78054 64 8 0 79401 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 318916

[startup+1.33522 s]
/proc/loadavg: 1.26 1.70 1.89 3/94 14375
/proc/meminfo: memFree=1268264/2055920 swapFree=4192812/4192956
[pid=14374] ppid=14372 vsize=389392 CPUtime=1.3
/proc/14374/stat : 14374 (VALCSP) R 14372 14374 13377 0 -1 4194304 95672 0 0 0 90 40 0 0 25 0 1 0 164924736 398737408 95650 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530236 0 0 4096 0 0 0 0 17 0 0 0
/proc/14374/statm: 97348 95650 64 8 0 97020 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 389392

[startup+2.97239 s]
/proc/loadavg: 1.26 1.70 1.89 3/94 14375
/proc/meminfo: memFree=1157800/2055920 swapFree=4192812/4192956
[pid=14374] ppid=14372 vsize=565364 CPUtime=2.93
/proc/14374/stat : 14374 (VALCSP) R 14372 14374 13377 0 -1 4194304 139662 0 0 0 233 60 0 0 25 0 1 0 164924736 578932736 139640 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134530278 0 0 4096 0 0 0 0 17 0 0 0
/proc/14374/statm: 141341 139640 64 8 0 141013 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 565364

[startup+6.25173 s]
/proc/loadavg: 1.26 1.70 1.89 3/94 14375
/proc/meminfo: memFree=802088/2055920 swapFree=4192812/4192956
[pid=14374] ppid=14372 vsize=917168 CPUtime=6.18
/proc/14374/stat : 14374 (VALCSP) R 14372 14374 13377 0 -1 4194304 227642 0 0 0 520 98 0 0 25 0 1 0 164924736 939180032 227620 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134531029 0 0 4096 0 0 0 0 17 0 0 0
/proc/14374/statm: 229292 227620 64 8 0 228964 0
Current children cumulated CPU time (s) 6.18
Current children cumulated vsize (KiB) 917168



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+6.45676 s]
/proc/loadavg: 1.32 1.70 1.89 3/94 14375
/proc/meminfo: memFree=695592/2055920 swapFree=4192812/4192956
[pid=14374] ppid=14372 vsize=952468 CPUtime=6.39
/proc/14374/stat : 14374 (VALCSP) R 14372 14374 13377 0 -1 4194304 236440 0 0 0 536 103 0 0 25 0 1 0 164924736 975327232 236418 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134531008 0 0 4096 0 0 0 0 17 0 0 0
/proc/14374/statm: 238117 236418 64 8 0 237789 0
Current children cumulated CPU time (s) 6.39
Current children cumulated vsize (KiB) 952468

Sending SIGTERM to process tree (bottom up)
Sleeping 2 seconds

Child ended because it received signal 15 (SIGTERM)
Real time (s): 6.60335
CPU time (s): 6.536
CPU user time (s): 5.36318
CPU system time (s): 1.17282
CPU usage (%): 98.9801
Max. virtual memory (cumulated for all children) (KiB): 952468

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

runsolver used 0.010998 s user time and 0.023996 s system time

The end



Launcher Data (download as text)




Begin job on node17 on Sun Jan  7 10:21:37 UTC 2007


IDJOB= 204110
IDBENCH= 4001
FILE ID= node17/204110-1168165295

PBS_JOBID= 3478309

Free space on /tmp= 66272 MiB

BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-3000-3000.xml
COMMAND LINE= /tmp/evaluation/204110-1168165295/VALCSP /tmp/evaluation/204110-1168165295/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-204110-1168165295 -o ROOT/results/node17/solver-204110-1168165295 -C 1800 -M 900  /tmp/evaluation/204110-1168165295/VALCSP /tmp/evaluation/204110-1168165295/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  2856bb6534c66b8fd5677f0eaa3dd113

RANDOM SEED= 361089819

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:       1651720 kB
Buffers:         49760 kB
Cached:         164576 kB
SwapCached:          0 kB
Active:         225220 kB
Inactive:       117344 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1651720 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           11912 kB
Writeback:           0 kB
Mapped:         156064 kB
Slab:            46212 kB
Committed_AS:  5038708 kB
PageTables:       2496 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= 66263 MiB



End job on node17 on Sun Jan  7 10:21:46 UTC 2007