Trace number 236625

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
Tramontane 2006-12-04? (MO) 1.67174 1.69327

General information on the benchmark

Namefisher/
FISCHER5-8-fair.xml
MD5SUM759b287a619b7d1444302c4a6aaa485e
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Satisfiable
(Un)Satisfiability was proved
Number of variables10482
Number of constraints9907
Maximum constraint arity3
Maximum domain size20001
Number of constraints which are defined in extension0
Number of constraints which are defined in intension9907
Global constraints used (with number of constraints)

Solver Data (download as text)

0.06	c 
0.06	c Parsing xml file
0.06	c 	domains...............    0
0.06	c 	variables........

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/node5/watcher-236625-1168344219 -o ROOT/results/node5/solver-236625-1168344219 -C 1800 -M 900 /tmp/evaluation/236625-1168344219/tramontane/bin/solver /tmp/evaluation/236625-1168344219/unknown.xml -res geom -f 3 -v 1 

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


[startup+0.103177 s]
/proc/loadavg: 1.92 1.98 2.11 2/88 21724
/proc/meminfo: memFree=1818520/2055920 swapFree=4192812/4192956
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0
/proc/loadavg: 1.92 1.98 2.11 2/88 21724
/proc/meminfo: memFree=1818520/2055920 swapFree=4192812/4192956
[pid=21723] ppid=21721 vsize=125804 CPUtime=0.19
/proc/21723/stat : 21723 (solver) R 21721 21723 21252 0 -1 4194304 30464 0 0 0 7 12 0 0 19 0 1 0 163036354 128823296 30432 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134804818 0 0 4096 0 0 0 0 17 1 0 0
/proc/21723/statm: 31451 30432 692 92 0 29795 0

[startup+0.511222 s]
/proc/loadavg: 1.92 1.98 2.11 2/88 21724
/proc/meminfo: memFree=1818520/2055920 swapFree=4192812/4192956
[pid=21723] ppid=21721 vsize=318004 CPUtime=0.49
/proc/21723/stat : 21723 (solver) R 21721 21723 21252 0 -1 4194304 78540 0 0 0 16 33 0 0 22 0 1 0 163036354 325636096 78508 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 4158556824 0 0 4096 0 0 0 0 17 1 0 0
/proc/21723/statm: 79501 78508 692 92 0 77845 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 318004

[startup+1.33232 s]
/proc/loadavg: 2.01 2.00 2.12 3/88 21724
/proc/meminfo: memFree=1123160/2055920 swapFree=4192812/4192956
[pid=21723] ppid=21721 vsize=829420 CPUtime=1.3
/proc/21723/stat : 21723 (solver) R 21721 21723 21252 0 -1 4194304 206397 0 0 0 46 84 0 0 25 0 1 0 163036354 849326080 206365 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134804841 0 0 4096 0 0 0 0 17 1 0 0
/proc/21723/statm: 207355 206365 692 92 0 205699 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 829420



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+1.53634 s]
/proc/loadavg: 2.01 2.00 2.12 3/88 21724
/proc/meminfo: memFree=865120/2055920 swapFree=4192812/4192956
[pid=21723] ppid=21721 vsize=958348 CPUtime=1.51
/proc/21723/stat : 21723 (solver) R 21721 21723 21252 0 -1 4194304 238601 0 0 0 53 98 0 0 25 0 1 0 163036354 981348352 238569 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134804823 0 0 4096 0 0 0 0 17 1 0 0
/proc/21723/statm: 239587 238569 692 92 0 237931 0
Current children cumulated CPU time (s) 1.51
Current children cumulated vsize (KiB) 958348

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 1.69327
CPU time (s): 1.67174
CPU user time (s): 0.538918
CPU system time (s): 1.13283
CPU usage (%): 98.729
Max. virtual memory (cumulated for all children) (KiB): 958348

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.538918
system time used= 1.13283
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 238601
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= 12
involuntary context switches= 42

runsolver used 0.003999 s user time and 0.014997 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Tue Jan  9 12:03:39 UTC 2007


IDJOB= 236625
IDBENCH= 6861
FILE ID= node5/236625-1168344219

PBS_JOBID= 3503213

Free space on /tmp= 66550 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fisher/FISCHER5-8-fair.xml
COMMAND LINE= /tmp/evaluation/236625-1168344219/tramontane/bin/solver /tmp/evaluation/236625-1168344219/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-236625-1168344219 -o ROOT/results/node5/solver-236625-1168344219 -C 1800 -M 900  /tmp/evaluation/236625-1168344219/tramontane/bin/solver /tmp/evaluation/236625-1168344219/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  759b287a619b7d1444302c4a6aaa485e

RANDOM SEED= 952274385

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.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:       1819000 kB
Buffers:         20560 kB
Cached:          83616 kB
SwapCached:          0 kB
Active:         136324 kB
Inactive:        45764 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1819000 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            5092 kB
Writeback:           0 kB
Mapped:          98196 kB
Slab:            39700 kB
Committed_AS:  4691240 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= 66550 MiB



End job on node5 on Tue Jan  9 12:03:41 UTC 2007