Trace number 280624

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) 0.030995 2.37716

General information on the benchmark

NameMaxCSP/pedigree/
sheep4r-4-3_ext.xml
MD5SUM059834bcc85163132960cf21f1c992ed
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints3634
Best CPU time to get the best result obtained on this benchmark38.0642
Satisfiable
(Un)Satisfiability was proved
Number of variables2686
Number of constraints3635
Maximum constraint arity3
Maximum domain size10
Number of constraints which are defined in extension3635
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/280624-1169306908/unknown.xml to /tmp/evaluation/280624-1169306908/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-280624-1169306908 -o ROOT/results/node5/solver-280624-1169306908 -C 2400 -M 900 /tmp/evaluation/280624-1169306908/solver.sh /tmp/evaluation/280624-1169306908/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: 2.04 2.01 2.00 5/87 25190
/proc/meminfo: memFree=882544/2055920 swapFree=4192812/4192956
[pid=25189] ppid=25187 vsize=18540 CPUtime=0
/proc/25189/stat : 25189 (runsolver) R 25187 25189 24312 0 -1 4194368 16 0 0 0 0 0 0 0 21 0 1 0 259305587 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 226913479975 0 0 4096 24578 0 0 0 17 1 0 0
/proc/25189/statm: 4635 279 244 17 0 2626 0

[startup+0.110375 s]
/proc/loadavg: 2.04 2.01 2.00 5/87 25190
/proc/meminfo: memFree=882544/2055920 swapFree=4192812/4192956
[pid=25189] ppid=25187 vsize=47556 CPUtime=0.01
/proc/25189/stat : 25189 (solver.sh) S 25187 25189 24312 0 -1 4194304 873 2245 0 0 0 0 0 1 25 0 1 0 259305587 48697344 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/25189/statm: 11889 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

[startup+0.518422 s]
/proc/loadavg: 2.04 2.01 2.00 5/87 25190
/proc/meminfo: memFree=882544/2055920 swapFree=4192812/4192956
[pid=25189] ppid=25187 vsize=47556 CPUtime=0.01
/proc/25189/stat : 25189 (solver.sh) S 25187 25189 24312 0 -1 4194304 873 2245 0 0 0 0 0 1 25 0 1 0 259305587 48697344 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/25189/statm: 11889 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

[startup+1.33952 s]
/proc/loadavg: 2.04 2.01 2.00 3/88 25207
/proc/meminfo: memFree=691240/2055920 swapFree=4192812/4192956
[pid=25189] ppid=25187 vsize=47556 CPUtime=0.01
/proc/25189/stat : 25189 (solver.sh) S 25187 25189 24312 0 -1 4194304 873 2245 0 0 0 0 0 1 25 0 1 0 259305587 48697344 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/25189/statm: 11889 361 245 79 0 217 0
[pid=25207] ppid=25189 vsize=398520 CPUtime=1.28
/proc/25207/stat : 25207 (toolbar) R 25189 25189 24312 0 -1 4194304 79201 0 0 0 95 33 0 0 25 0 1 0 259305591 408084480 73606 18446744073709551615 134512640 135242688 4294956576 18446744073709551615 134884559 0 0 4096 2 0 0 0 17 1 0 0
/proc/25207/statm: 99630 73606 51 178 0 99448 0
Current children cumulated CPU time (s) 1.29
Current children cumulated vsize (KiB) 446076



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+2.36464 s]
/proc/loadavg: 2.04 2.01 2.00 3/88 25207
/proc/meminfo: memFree=77096/2055920 swapFree=4192812/4192956
[pid=25189] ppid=25187 vsize=47556 CPUtime=0.01
/proc/25189/stat : 25189 (solver.sh) S 25187 25189 24312 0 -1 4194304 873 2245 0 0 0 0 0 1 25 0 1 0 259305587 48697344 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/25189/statm: 11889 361 245 79 0 217 0
[pid=25207] ppid=25189 vsize=907684 CPUtime=2.29
/proc/25207/stat : 25207 (toolbar) R 25189 25189 24312 0 -1 4194304 206440 0 0 0 144 85 0 0 25 0 1 0 259305591 929468416 200845 18446744073709551615 134512640 135242688 4294956576 18446744073709551615 134643111 0 0 4096 2 0 0 0 17 1 0 0
/proc/25207/statm: 226921 200845 52 178 0 226739 0
Current children cumulated CPU time (s) 2.3
Current children cumulated vsize (KiB) 955240

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 2.37716
CPU time (s): 0.030995
CPU user time (s): 0.012998
CPU system time (s): 0.017997
CPU usage (%): 1.30387
Max. virtual memory (cumulated for all children) (KiB): 955240

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.012998
system time used= 0.017997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3118
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= 62
involuntary context switches= 26

runsolver used 0.004999 s user time and 0.018997 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Sat Jan 20 15:28:28 UTC 2007


IDJOB= 280624
IDBENCH= 11880
IDSOLVER= 71
FILE ID= node5/280624-1169306908

PBS_JOBID= 3609906

Free space on /tmp= 66045 MiB

SOLVER NAME= Toolbar_MaxSat 2007-01-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/pedigree/sheep4r-4-3_ext.xml
COMMAND LINE= /tmp/evaluation/280624-1169306908/solver.sh /tmp/evaluation/280624-1169306908/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node5/convwatcher-280624-1169306908 -o ROOT/results/node5/conversion-280624-1169306908 -C 600 -M 900 /tmp/evaluation/280624-1169306908/translate /tmp/evaluation/280624-1169306908/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= f843f34905a307bcc0c6a322bc802c9d
MD5SUM BENCH=  059834bcc85163132960cf21f1c992ed

RANDOM SEED= 393164229

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:        883024 kB
Buffers:         57564 kB
Cached:         972704 kB
SwapCached:          0 kB
Active:          91428 kB
Inactive:       992320 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        883024 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            6772 kB
Writeback:           0 kB
Mapped:          74468 kB
Slab:            73784 kB
Committed_AS:  7381276 kB
PageTables:       2200 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 node5 on Sat Jan 20 15:28:34 UTC 2007