Trace number 236507

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
Mistral 2006-12-04Signal 1.18382 1.27279

General information on the benchmark

Namefisher/
FISCHER1-5-fair.xml
MD5SUM1547fe3c40d31d02d77bf0e193480403
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.179971
SatisfiableNO
(Un)Satisfiability was proved
Number of variables1423
Number of constraints1336
Maximum constraint arity3
Maximum domain size20001
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1336
Global constraints used (with number of constraints)

Solver Data (download as text)

0.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.01	c 	variables............. 0.31
0.32	c 	predicates...test
0.34	..test
0.34	test
0.34	.test
0.34	test
0.34	.test
0.34	test
0.34	...test
0.34	test
0.34	..    0
0.34	c 	constraints.solver: models/src/MyCallback.h:681: virtual void CSPXMLParser::MyCallback::endConstraint(): Assertion `predScope[idcur][k][l] < predMaxSize' failed.

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/node26/watcher-236507-1168343703 -o ROOT/results/node26/solver-236507-1168343703 -C 1800 -M 900 /tmp/evaluation/236507-1168343703/mistral/bin/solver /tmp/evaluation/236507-1168343703/unknown.xml -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

/proc/loadavg: 0.94 1.42 1.62 5/97 5651
/proc/meminfo: memFree=1361024/2055920 swapFree=4192812/4192956
[pid=5650] ppid=5648 vsize=6792 CPUtime=0
/proc/5650/stat : 5650 (solver) R 5648 5650 5362 0 -1 4194304 423 0 0 0 0 0 0 0 18 0 1 0 182764589 6955008 402 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 12556151 0 0 4096 0 0 0 0 17 1 0 0
/proc/5650/statm: 1698 402 363 92 0 30 0

[startup+0.104133 s]
/proc/loadavg: 0.94 1.42 1.62 5/97 5651
/proc/meminfo: memFree=1361024/2055920 swapFree=4192812/4192956
[pid=5650] ppid=5648 vsize=64592 CPUtime=0.09
/proc/5650/stat : 5650 (solver) R 5648 5650 5362 0 -1 4194304 15201 0 0 0 3 6 0 0 18 0 1 0 182764589 66142208 15169 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 13026939 0 0 4096 0 0 0 0 17 1 0 0
/proc/5650/statm: 16188 15177 692 92 0 14532 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 64592

[startup+0.512174 s]
/proc/loadavg: 0.94 1.42 1.62 5/97 5651
/proc/meminfo: memFree=1361024/2055920 swapFree=4192812/4192956
[pid=5650] ppid=5648 vsize=196856 CPUtime=0.46
/proc/5650/stat : 5650 (solver) R 5648 5650 5362 0 -1 4195840 48306 0 4 0 11 35 0 0 18 0 1 0 182764589 201580544 48277 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/5650/statm: 49214 48277 719 92 0 47558 0
Current children cumulated CPU time (s) 0.46
Current children cumulated vsize (KiB) 196856

Child ended because it received signal 6 (SIGABRT)
Real time (s): 1.27279
CPU time (s): 1.18382
CPU user time (s): 0.115982
CPU system time (s): 1.06784
CPU usage (%): 93.0099
Max. virtual memory (cumulated for all children) (KiB): 196856

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.115982
system time used= 1.06784
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 48353
page faults= 8
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 22
involuntary context switches= 88

runsolver used 0.004999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node26 on Tue Jan  9 11:55:03 UTC 2007


IDJOB= 236507
IDBENCH= 6852
FILE ID= node26/236507-1168343703

PBS_JOBID= 3503458

Free space on /tmp= 66537 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fisher/FISCHER1-5-fair.xml
COMMAND LINE= /tmp/evaluation/236507-1168343703/mistral/bin/solver /tmp/evaluation/236507-1168343703/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node26/watcher-236507-1168343703 -o ROOT/results/node26/solver-236507-1168343703 -C 1800 -M 900  /tmp/evaluation/236507-1168343703/mistral/bin/solver /tmp/evaluation/236507-1168343703/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  1547fe3c40d31d02d77bf0e193480403

RANDOM SEED= 733938406

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.236
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.236
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:       1361632 kB
Buffers:         26152 kB
Cached:         537636 kB
SwapCached:          0 kB
Active:         146128 kB
Inactive:       495408 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1361632 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            6312 kB
Writeback:           0 kB
Mapped:         106428 kB
Slab:            37484 kB
Committed_AS:  4404092 kB
PageTables:       2336 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= 66351 MiB



End job on node26 on Tue Jan  9 11:55:05 UTC 2007