Trace number 282703

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
Toolbar_MaxSat 2007-01-19? (MO) 2.2 2.27477

General information on the benchmark

NameMaxCSP/celar/scens/
scenw-06-24_ext.xml
MD5SUM95b6a5d3e9a91c69b60abc9fffa0c3ba
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints1181
Best CPU time to get the best result obtained on this benchmark29.2346
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints1203
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension1203
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/282703-1169321729/unknown.xml to /tmp/evaluation/282703-1169321729/unknown.wcsp

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node5/watcher-282703-1169321729 -o ROOT/results/node5/solver-282703-1169321729 -C 2400 -M 900 /tmp/evaluation/282703-1169321729/solver.sh /tmp/evaluation/282703-1169321729/unknown 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 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.92 1.98 1.99 5/93 29308
/proc/meminfo: memFree=1388528/2055920 swapFree=4192812/4192956
[pid=29307] ppid=29305 vsize=18540 CPUtime=0
/proc/29307/stat : 29307 (runsolver) R 29305 29307 28627 0 -1 4194368 16 0 0 0 0 0 0 0 21 0 1 0 260787499 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 226913479975 0 0 4096 24578 0 0 0 17 1 0 0
/proc/29307/statm: 4635 279 244 17 0 2626 0

[startup+0.110638 s]
/proc/loadavg: 1.92 1.98 1.99 5/93 29308
/proc/meminfo: memFree=1388528/2055920 swapFree=4192812/4192956
[pid=29307] ppid=29305 vsize=47556 CPUtime=0.01
/proc/29307/stat : 29307 (solver.sh) S 29305 29307 28627 0 -1 4194304 873 2245 0 0 0 0 0 1 25 0 1 0 260787499 48697344 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/29307/statm: 11889 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

[startup+0.518693 s]
/proc/loadavg: 1.92 1.98 1.99 5/93 29308
/proc/meminfo: memFree=1388528/2055920 swapFree=4192812/4192956
[pid=29307] ppid=29305 vsize=47556 CPUtime=0.16
/proc/29307/stat : 29307 (solver.sh) S 29305 29307 28627 0 -1 4194304 901 2920 0 0 0 1 13 2 15 0 1 0 260787499 48697344 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/29307/statm: 11889 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.16
Current children cumulated vsize (KiB) 47556

[startup+1.33978 s]
/proc/loadavg: 1.92 1.98 1.99 3/94 29329
/proc/meminfo: memFree=877736/2055920 swapFree=4192812/4192956
[pid=29307] ppid=29305 vsize=47556 CPUtime=0.16
/proc/29307/stat : 29307 (solver.sh) S 29305 29307 28627 0 -1 4194304 901 2920 0 0 0 1 13 2 15 0 1 0 260787499 48697344 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/29307/statm: 11889 361 245 79 0 217 0
[pid=29326] ppid=29307 vsize=568828 CPUtime=1.13
/proc/29326/stat : 29326 (toolbar) R 29307 29307 28627 0 -1 4194304 142089 2081 0 0 37 62 13 1 25 0 1 0 260787518 582479872 142055 18446744073709551615 134512640 135242688 4294956608 18446744073709551615 135002290 0 0 4096 0 0 0 0 17 1 0 0
/proc/29326/statm: 142207 142055 57 178 0 142025 0
Current children cumulated CPU time (s) 1.29
Current children cumulated vsize (KiB) 616384



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+2.25789 s]
/proc/loadavg: 1.92 1.98 1.99 3/94 29329
/proc/meminfo: memFree=618856/2055920 swapFree=4192812/4192956
[pid=29307] ppid=29305 vsize=47556 CPUtime=0.16
/proc/29307/stat : 29307 (solver.sh) S 29305 29307 28627 0 -1 4194304 901 2920 0 0 0 1 13 2 15 0 1 0 260787499 48697344 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/29307/statm: 11889 361 245 79 0 217 0
[pid=29326] ppid=29307 vsize=874692 CPUtime=2.04
/proc/29326/stat : 29326 (toolbar) R 29307 29307 28627 0 -1 4194304 191613 2081 0 0 106 84 13 1 25 0 1 0 260787518 895684608 191578 18446744073709551615 134512640 135242688 4294956608 18446744073709551615 134884559 0 0 4096 2 0 0 0 17 1 0 0
/proc/29326/statm: 218673 191578 67 178 0 218491 0
Current children cumulated CPU time (s) 2.2
Current children cumulated vsize (KiB) 922248

Sending SIGTERM to process tree (bottom up)

Child ended because it received signal 15 (SIGTERM)

!!! problem with CPU time !!!
wait4(...,&childrusage) returns 29307 and gives childrusage.ru_utime.tv_sec=0 childrusage.ru_utime.tv_usec=141978 childrusage.ru_stime.tv_sec=0 childrusage.ru_stime.tv_usec=40993
CPU time returned by wait4() is 0.182971
while last known CPU time is 2.2

Solver probably didn't/couldn't wait for its children
Using last known CPU time as value...

Real time (s): 2.27477
CPU time (s): 2.2
CPU user time (s): 1.32
CPU system time (s): 0.88
CPU usage (%): 96.7132
Max. virtual memory (cumulated for all children) (KiB): 922248

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.141978
system time used= 0.040993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3821
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= 66
involuntary context switches= 37

runsolver used 0.006998 s user time and 0.018997 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Sat Jan 20 19:35:30 UTC 2007


IDJOB= 282703
IDBENCH= 12880
IDSOLVER= 71
FILE ID= node5/282703-1169321729

PBS_JOBID= 3610075

Free space on /tmp= 66561 MiB

SOLVER NAME= Toolbar_MaxSat 2007-01-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/celar/scens/scenw-06-24_ext.xml
COMMAND LINE= /tmp/evaluation/282703-1169321729/solver.sh /tmp/evaluation/282703-1169321729/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node5/convwatcher-282703-1169321729 -o ROOT/results/node5/conversion-282703-1169321729 -C 600 -M 900 /tmp/evaluation/282703-1169321729/translate /tmp/evaluation/282703-1169321729/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-282703-1169321729 -o ROOT/results/node5/solver-282703-1169321729 -C 2400 -M 900  /tmp/evaluation/282703-1169321729/solver.sh /tmp/evaluation/282703-1169321729/unknown

META MD5SUM SOLVER= f843f34905a307bcc0c6a322bc802c9d
MD5SUM BENCH=  95b6a5d3e9a91c69b60abc9fffa0c3ba

RANDOM SEED= 477197926

TIME LIMIT= 2400 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.240
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.240
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:       1389008 kB
Buffers:         59052 kB
Cached:         453872 kB
SwapCached:          0 kB
Active:         164468 kB
Inactive:       424292 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1389008 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3084 kB
Writeback:           0 kB
Mapped:         104900 kB
Slab:            62964 kB
Committed_AS:  8443880 kB
PageTables:       2272 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 node5 on Sat Jan 20 19:35:33 UTC 2007