Trace number 249215

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-04Signal 0.022996 0.028668

General information on the benchmark

Nameprimes/primes-15/
primes-15-40-2-1.xml
MD5SUM43a80e969e404258723a3990da76367b
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.021996
SatisfiableYES
(Un)Satisfiability was proved
Number of variables100
Number of constraints40
Maximum constraint arity3
Maximum domain size46
Number of constraints which are defined in extension0
Number of constraints which are defined in intension40
Global constraints used (with number of constraints)

Solver Data (download as text)

0.02	c 
0.02	c Parsing xml file
0.02	c 	domains...............    0
0.02	c 	variables.............    0
0.02	c 	predicates..test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	test
0.02	.    0
0.02	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/node10/watcher-249215-1168720270 -o ROOT/results/node10/solver-249215-1168720270 -C 1800 -M 900 /tmp/evaluation/249215-1168720270/tramontane/bin/solver /tmp/evaluation/249215-1168720270/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

/proc/loadavg: 1.72 1.93 1.97 2/94 23744
/proc/meminfo: memFree=1054800/2055920 swapFree=4178232/4192956
[pid=23743] ppid=23741 vsize=540 CPUtime=0
/proc/23743/stat : 23743 (solver) R 23741 23743 23271 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 220422157 552960 26 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 8905508 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/23743/statm: 135 26 21 92 0 18 0

Child ended because it received signal 6 (SIGABRT)
Real time (s): 0.028668
CPU time (s): 0.022996
CPU user time (s): 0.012998
CPU system time (s): 0.009998
CPU usage (%): 80.215
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.012998
system time used= 0.009998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 937
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= 1

runsolver used 0.003999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Sat Jan 13 20:31:10 UTC 2007


IDJOB= 249215
IDBENCH= 11766
IDSOLVER= 85
FILE ID= node10/249215-1168720270

PBS_JOBID= 3547481

Free space on /tmp= 66561 MiB

SOLVER NAME= Tramontane 2006-12-04
BENCH NAME= HOME/pub/bench/CPAI06/primes/primes-15/primes-15-40-2-1.xml
COMMAND LINE= /tmp/evaluation/249215-1168720270/tramontane/bin/solver /tmp/evaluation/249215-1168720270/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-249215-1168720270 -o ROOT/results/node10/solver-249215-1168720270 -C 1800 -M 900  /tmp/evaluation/249215-1168720270/tramontane/bin/solver /tmp/evaluation/249215-1168720270/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  43a80e969e404258723a3990da76367b

RANDOM SEED= 449934034

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.232
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.232
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:       1055280 kB
Buffers:         20360 kB
Cached:         234116 kB
SwapCached:       2360 kB
Active:         715880 kB
Inactive:       212648 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1055280 kB
SwapTotal:     4192956 kB
SwapFree:      4178232 kB
Dirty:            3316 kB
Writeback:           0 kB
Mapped:         691412 kB
Slab:            55468 kB
Committed_AS:  7304476 kB
PageTables:       3560 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= 66561 MiB



End job on node10 on Sat Jan 13 20:31:10 UTC 2007