Trace number 276673

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.07 1.14157

General information on the benchmark

Nametightness/tightness0.65/
rand-2-40-40-135-650-16_ext.xml
MD5SUMfcab047e9b83f82daad7838afbfcb22c
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints134
Best CPU time to get the best result obtained on this benchmark204.3
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables40
Number of constraints135
Maximum constraint arity2
Maximum domain size40
Number of constraints which are defined in extension135
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/276673-1169243890/unknown.xml to /tmp/evaluation/276673-1169243890/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/node30/watcher-276673-1169243890 -o ROOT/results/node30/solver-276673-1169243890 -C 2400 -M 900 /tmp/evaluation/276673-1169243890/solver.sh /tmp/evaluation/276673-1169243890/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: 0.85 0.97 1.05 5/82 28441
/proc/meminfo: memFree=1529280/2055920 swapFree=4167328/4192956
[pid=28440] ppid=28436 vsize=8652 CPUtime=0
/proc/28440/stat : 28440 (solver.sh) S 28436 28440 28308 0 -1 4194304 347 0 0 0 0 0 0 0 18 0 1 0 272783095 8859648 280 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 264907189082 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/28440/statm: 2163 280 208 79 0 156 0
[pid=28443] ppid=28440 vsize=8688 CPUtime=0
/proc/28443/stat : 28443 (solver.sh) R 28440 28440 28308 0 -1 4194368 50 244 0 0 0 0 0 0 19 0 1 0 272783096 8896512 288 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 264907582111 0 65536 4096 73728 0 0 0 17 0 0 0
/proc/28443/statm: 2172 288 210 79 0 165 0
[pid=28446] ppid=28443 vsize=8688 CPUtime=0
/proc/28446/stat : 28446 (solver.sh) R 28443 28440 28308 0 -1 4194368 10 0 0 0 0 0 0 0 19 0 1 0 272783096 8896512 288 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 264907750066 0 0 4096 73728 0 0 0 17 0 0 0
/proc/28446/statm: 2172 288 210 79 0 165 0

[startup+0.104376 s]
/proc/loadavg: 0.85 0.97 1.05 5/82 28441
/proc/meminfo: memFree=1529280/2055920 swapFree=4167328/4192956
[pid=28440] ppid=28436 vsize=47556 CPUtime=0.01
/proc/28440/stat : 28440 (solver.sh) S 28436 28440 28308 0 -1 4194304 874 2410 0 0 0 0 0 1 18 0 1 0 272783095 48697344 362 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 264907189082 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/28440/statm: 11889 362 246 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

[startup+0.512365 s]
/proc/loadavg: 0.85 0.97 1.05 5/82 28441
/proc/meminfo: memFree=1529280/2055920 swapFree=4167328/4192956
[pid=28440] ppid=28436 vsize=47556 CPUtime=0.21
/proc/28440/stat : 28440 (solver.sh) S 28436 28440 28308 0 -1 4194304 902 2908 0 0 0 0 18 3 16 0 1 0 272783095 48697344 362 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 264907189082 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/28440/statm: 11889 362 246 79 0 217 0
Current children cumulated CPU time (s) 0.21
Current children cumulated vsize (KiB) 47556



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+1.12441 s]
/proc/loadavg: 0.85 0.97 1.05 3/89 28484
/proc/meminfo: memFree=994880/2055920 swapFree=4167328/4192956
[pid=28440] ppid=28436 vsize=47556 CPUtime=0.21
/proc/28440/stat : 28440 (solver.sh) S 28436 28440 28308 0 -1 4194304 902 2908 0 0 0 0 18 3 16 0 1 0 272783095 48697344 362 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 264907189082 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/28440/statm: 11889 362 246 79 0 217 0
[pid=28481] ppid=28440 vsize=880020 CPUtime=0.86
/proc/28481/stat : 28481 (toolbar) R 28440 28440 28308 0 -1 4194304 131819 3095 0 0 3 53 29 1 21 0 1 0 272783119 901140480 131785 18446744073709551615 134512640 135242688 4294956608 18446744073709551615 134580758 0 0 4096 0 0 0 0 17 1 0 0
/proc/28481/statm: 220005 131785 53 178 0 219823 0
Current children cumulated CPU time (s) 1.07
Current children cumulated vsize (KiB) 927576

Sending SIGTERM to process tree (bottom up)

Child ended because it received signal 15 (SIGTERM)

!!! problem with CPU time !!!
wait4(...,&childrusage) returns 28440 and gives childrusage.ru_utime.tv_sec=0 childrusage.ru_utime.tv_usec=191970 childrusage.ru_stime.tv_sec=0 childrusage.ru_stime.tv_usec=44993
CPU time returned by wait4() is 0.236963
while last known CPU time is 1.07

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

Real time (s): 1.14157
CPU time (s): 1.07
CPU user time (s): 0.5
CPU system time (s): 0.57
CPU usage (%): 93.7305
Max. virtual memory (cumulated for all children) (KiB): 927576

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.19197
system time used= 0.044993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3810
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= 53
involuntary context switches= 34

runsolver used 0.004999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node30 on Fri Jan 19 21:58:11 UTC 2007


IDJOB= 276673
IDBENCH= 5937
IDSOLVER= 71
FILE ID= node30/276673-1169243890

PBS_JOBID= 3589333

Free space on /tmp= 66560 MiB

SOLVER NAME= Toolbar_MaxSat 2007-01-19
BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.65/rand-2-40-40-135-650-16_ext.xml
COMMAND LINE= /tmp/evaluation/276673-1169243890/solver.sh /tmp/evaluation/276673-1169243890/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node30/convwatcher-276673-1169243890 -o ROOT/results/node30/conversion-276673-1169243890 -C 600 -M 900 /tmp/evaluation/276673-1169243890/translate /tmp/evaluation/276673-1169243890/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node30/watcher-276673-1169243890 -o ROOT/results/node30/solver-276673-1169243890 -C 2400 -M 900  /tmp/evaluation/276673-1169243890/solver.sh /tmp/evaluation/276673-1169243890/unknown

META MD5SUM SOLVER= f843f34905a307bcc0c6a322bc802c9d
MD5SUM BENCH=  fcab047e9b83f82daad7838afbfcb22c

RANDOM SEED= 559163589

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.234
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.234
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:       1525832 kB
Buffers:         38296 kB
Cached:         376380 kB
SwapCached:       2164 kB
Active:         175508 kB
Inactive:       276568 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1525832 kB
SwapTotal:     4192956 kB
SwapFree:      4167328 kB
Dirty:            6444 kB
Writeback:           0 kB
Mapped:          55896 kB
Slab:            62792 kB
Committed_AS:  4955528 kB
PageTables:       2204 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= 66555 MiB



End job on node30 on Fri Jan 19 21:58:13 UTC 2007