Trace number 280579

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) 1.06 1.14231

General information on the benchmark

NameMaxCSP/pedigree/
pedck350_ext.xml
MD5SUMae320f76604da74f15a9a28d28fd5000
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints576
Best CPU time to get the best result obtained on this benchmark5.03523
Satisfiable
(Un)Satisfiability was proved
Number of variables351
Number of constraints578
Maximum constraint arity3
Maximum domain size10
Number of constraints which are defined in extension578
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/280579-1169306764/unknown.xml to /tmp/evaluation/280579-1169306764/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/node4/watcher-280579-1169306764 -o ROOT/results/node4/solver-280579-1169306764 -C 2400 -M 900 /tmp/evaluation/280579-1169306764/solver.sh /tmp/evaluation/280579-1169306764/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 2.01 1.99 5/87 5597
/proc/meminfo: memFree=803752/2055920 swapFree=4182144/4192956
[pid=5596] ppid=5594 vsize=8560 CPUtime=0
/proc/5596/stat : 5596 (solver.sh) R 5594 5596 5049 0 -1 4194304 308 0 0 0 0 0 0 0 20 0 1 0 279072008 8765440 253 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 259913402255 0 0 4096 8192 0 0 0 17 1 0 0
/proc/5596/statm: 2140 253 197 79 0 133 0

[startup+0.105767 s]
/proc/loadavg: 1.92 2.01 1.99 5/87 5597
/proc/meminfo: memFree=803752/2055920 swapFree=4182144/4192956
[pid=5596] ppid=5594 vsize=47552 CPUtime=0.01
/proc/5596/stat : 5596 (solver.sh) S 5594 5596 5049 0 -1 4194304 871 2245 0 0 0 0 0 1 21 0 1 0 279072008 48693248 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 259912821594 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/5596/statm: 11888 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47552

[startup+0.513805 s]
/proc/loadavg: 1.92 2.01 1.99 5/87 5597
/proc/meminfo: memFree=803752/2055920 swapFree=4182144/4192956
[pid=5596] ppid=5594 vsize=47552 CPUtime=0.33
/proc/5596/stat : 5596 (solver.sh) S 5594 5596 5049 0 -1 4194304 899 6572 0 0 0 0 28 5 15 0 1 0 279072008 48693248 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 259912821594 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/5596/statm: 11888 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.33
Current children cumulated vsize (KiB) 47552



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+1.12587 s]
/proc/loadavg: 1.93 2.01 1.99 3/88 5618
/proc/meminfo: memFree=453088/2055920 swapFree=4182144/4192956
[pid=5596] ppid=5594 vsize=47552 CPUtime=0.33
/proc/5596/stat : 5596 (solver.sh) S 5594 5596 5049 0 -1 4194304 899 6572 0 0 0 0 28 5 15 0 1 0 279072008 48693248 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 259912821594 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/5596/statm: 11888 361 245 79 0 217 0
[pid=5615] ppid=5596 vsize=900656 CPUtime=0.73
/proc/5615/stat : 5615 (toolbar) R 5596 5596 5049 0 -1 4194304 86307 3461 0 0 2 35 35 1 19 0 1 0 279072044 922271744 86273 18446744073709551615 134512640 135242688 4294956608 18446744073709551615 134580758 0 0 4096 0 0 0 0 17 1 0 0
/proc/5615/statm: 225164 86273 53 178 0 224982 0
Current children cumulated CPU time (s) 1.06
Current children cumulated vsize (KiB) 948208

Sending SIGTERM to process tree (bottom up)

Child ended because it received signal 15 (SIGTERM)

!!! problem with CPU time !!!
wait4(...,&childrusage) returns 5596 and gives childrusage.ru_utime.tv_sec=0 childrusage.ru_utime.tv_usec=293955 childrusage.ru_stime.tv_sec=0 childrusage.ru_stime.tv_usec=61990
CPU time returned by wait4() is 0.355945
while last known CPU time is 1.06

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

Real time (s): 1.14231
CPU time (s): 1.06
CPU user time (s): 0.65
CPU system time (s): 0.41
CPU usage (%): 92.7942
Max. virtual memory (cumulated for all children) (KiB): 948208

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.293955
system time used= 0.06199
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 7471
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= 65
involuntary context switches= 32

runsolver used 0.002999 s user time and 0.015997 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Sat Jan 20 15:26:04 UTC 2007


IDJOB= 280579
IDBENCH= 11875
IDSOLVER= 71
FILE ID= node4/280579-1169306764

PBS_JOBID= 3609917

Free space on /tmp= 66046 MiB

SOLVER NAME= Toolbar_MaxSat 2007-01-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/pedigree/pedck350_ext.xml
COMMAND LINE= /tmp/evaluation/280579-1169306764/solver.sh /tmp/evaluation/280579-1169306764/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node4/convwatcher-280579-1169306764 -o ROOT/results/node4/conversion-280579-1169306764 -C 600 -M 900 /tmp/evaluation/280579-1169306764/translate /tmp/evaluation/280579-1169306764/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-280579-1169306764 -o ROOT/results/node4/solver-280579-1169306764 -C 2400 -M 900  /tmp/evaluation/280579-1169306764/solver.sh /tmp/evaluation/280579-1169306764/unknown

META MD5SUM SOLVER= f843f34905a307bcc0c6a322bc802c9d
MD5SUM BENCH=  ae320f76604da74f15a9a28d28fd5000

RANDOM SEED= 645085118

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.223
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.223
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:        804232 kB
Buffers:         67128 kB
Cached:        1046844 kB
SwapCached:       2180 kB
Active:         208272 kB
Inactive:       953336 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        804232 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:            2400 kB
Writeback:           0 kB
Mapped:          59432 kB
Slab:            74792 kB
Committed_AS:  8027436 kB
PageTables:       2436 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= 66041 MiB



End job on node4 on Sat Jan 20 15:26:06 UTC 2007