Trace number 237863

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.014996 0.0213929

General information on the benchmark

Namehaystacks/
haystacks_04.xml
MD5SUMd27edd6530026bc4e9b6a215c658ef2b
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.016997
SatisfiableNO
(Un)Satisfiability was proved
Number of variables16
Number of constraints27
Maximum constraint arity2
Maximum domain size4
Number of constraints which are defined in extension0
Number of constraints which are defined in intension27
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
0.01	c 	predicates....test
0.01	.....test
0.01	...    0
0.01	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/node55/watcher-237863-1168718841 -o ROOT/results/node55/solver-237863-1168718841 -C 1800 -M 900 /tmp/evaluation/237863-1168718841/tramontane/bin/solver /tmp/evaluation/237863-1168718841/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: 2.02 2.00 1.77 5/74 4727
/proc/meminfo: memFree=911008/2055920 swapFree=4192192/4192956
[pid=4726] ppid=4724 vsize=540 CPUtime=0
/proc/4726/stat : 4726 (solver) R 4724 4726 3887 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 220282434 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 6849316 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/4726/statm: 135 26 21 92 0 18 0

Child ended because it received signal 6 (SIGABRT)
Real time (s): 0.0213929
CPU time (s): 0.014996
CPU user time (s): 0.006998
CPU system time (s): 0.007998
CPU usage (%): 70.0979
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.006998
system time used= 0.007998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 908
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.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node55 on Sat Jan 13 20:07:22 UTC 2007


IDJOB= 237863
IDBENCH= 6967
IDSOLVER= 85
FILE ID= node55/237863-1168718841

PBS_JOBID= 3547613

Free space on /tmp= 66555 MiB

SOLVER NAME= Tramontane 2006-12-04
BENCH NAME= HOME/pub/bench/CPAI06/haystacks/haystacks_04.xml
COMMAND LINE= /tmp/evaluation/237863-1168718841/tramontane/bin/solver /tmp/evaluation/237863-1168718841/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node55/watcher-237863-1168718841 -o ROOT/results/node55/solver-237863-1168718841 -C 1800 -M 900  /tmp/evaluation/237863-1168718841/tramontane/bin/solver /tmp/evaluation/237863-1168718841/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  d27edd6530026bc4e9b6a215c658ef2b

RANDOM SEED= 871100169

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.218
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	: 5931.00
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.218
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:        911488 kB
Buffers:         27112 kB
Cached:         195184 kB
SwapCached:        268 kB
Active:         869356 kB
Inactive:       199672 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        911488 kB
SwapTotal:     4192956 kB
SwapFree:      4192192 kB
Dirty:            2952 kB
Writeback:           0 kB
Mapped:         856764 kB
Slab:            59300 kB
Committed_AS:  5761920 kB
PageTables:       3340 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 node55 on Sat Jan 13 20:07:22 UTC 2007