Trace number 219002

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-04SAT 2.32365 2.32472

General information on the benchmark

NamechessboardColoration/
cc-6-6-3.xml
MD5SUMf0eb4bbce4d0e24d3908b998a1ae22dc
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.032994
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables36
Number of constraints225
Maximum constraint arity4
Maximum domain size3
Number of constraints which are defined in extension0
Number of constraints which are defined in intension225
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............    0
0.01	c 	constraints........... 0.03
0.03	c Allocating memory
0.03	c 
0.03	c time limit = -1
0.03	c heuristic = dom/wdeg
0.03	c restart policy = No restart
0.03	c 
0.03	c Solving
0.03	c
2.32	s SATISFIABLE
2.32	v 0 0 0 0 0 0 0 1 1 1 1 2 1 1 0 2 2 1 0 2 2 1 2 1 1 0 2 2 1 2 2 2 0 2 1 1
2.32	d          SAT     45434 BTS       2.3 s

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node19/watcher-219002-1168253825 -o ROOT/results/node19/solver-219002-1168253825 -C 1800 -M 900 /tmp/evaluation/219002-1168253825/mistral/bin/solver /tmp/evaluation/219002-1168253825/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: 1.28 1.75 1.90 5/87 17174
/proc/meminfo: memFree=1823112/2055920 swapFree=4171244/4192956
[pid=17173] ppid=17171 vsize=6792 CPUtime=0
/proc/17173/stat : 17173 (solver) R 17171 17173 16929 0 -1 4194304 420 0 0 0 0 0 0 0 18 0 1 0 173777646 6955008 399 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7453572 0 0 4096 0 0 0 0 17 1 0 0
/proc/17173/statm: 1698 399 362 92 0 30 0

[startup+0.104397 s]
/proc/loadavg: 1.28 1.75 1.90 5/87 17174
/proc/meminfo: memFree=1823112/2055920 swapFree=4171244/4192956
[pid=17173] ppid=17171 vsize=7844 CPUtime=0.09
/proc/17173/stat : 17173 (solver) R 17171 17173 16929 0 -1 4194304 1039 0 0 0 9 0 0 0 18 0 1 0 173777646 8032256 1007 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134799371 0 0 4096 0 0 0 0 17 1 0 0
/proc/17173/statm: 1961 1007 718 92 0 305 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7844

[startup+0.514474 s]
/proc/loadavg: 1.28 1.75 1.90 5/87 17174
/proc/meminfo: memFree=1823112/2055920 swapFree=4171244/4192956
[pid=17173] ppid=17171 vsize=7848 CPUtime=0.5
/proc/17173/stat : 17173 (solver) R 17171 17173 16929 0 -1 4194304 1040 0 0 0 50 0 0 0 22 0 1 0 173777646 8036352 1008 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134712662 0 0 4096 0 0 0 0 17 1 0 0
/proc/17173/statm: 1962 1008 718 92 0 306 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 7848

[startup+1.33463 s]
/proc/loadavg: 1.28 1.75 1.90 3/87 17174
/proc/meminfo: memFree=1822088/2055920 swapFree=4171244/4192956
[pid=17173] ppid=17171 vsize=7848 CPUtime=1.32
/proc/17173/stat : 17173 (solver) R 17171 17173 16929 0 -1 4194304 1040 0 0 0 132 0 0 0 25 0 1 0 173777646 8036352 1008 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134640920 0 0 4096 0 0 0 0 17 1 0 0
/proc/17173/statm: 1962 1008 718 92 0 306 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 7848

Child status: 0
Real time (s): 2.32472
CPU time (s): 2.32365
CPU user time (s): 2.31565
CPU system time (s): 0.007998
CPU usage (%): 99.9538
Max. virtual memory (cumulated for all children) (KiB): 7848

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.31565
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= 1050
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= 106

runsolver used 0.001999 s user time and 0.014997 s system time

The end

Launcher Data (download as text)

Begin job on node19 on Mon Jan  8 10:57:08 UTC 2007


IDJOB= 219002
IDBENCH= 5272
FILE ID= node19/219002-1168253825

PBS_JOBID= 3481721

Free space on /tmp= 66318 MiB

BENCH NAME= HOME/pub/bench/CPAI06/chessboardColoration/cc-6-6-3.xml
COMMAND LINE= /tmp/evaluation/219002-1168253825/mistral/bin/solver /tmp/evaluation/219002-1168253825/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node19/watcher-219002-1168253825 -o ROOT/results/node19/solver-219002-1168253825 -C 1800 -M 900  /tmp/evaluation/219002-1168253825/mistral/bin/solver /tmp/evaluation/219002-1168253825/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  f0eb4bbce4d0e24d3908b998a1ae22dc

RANDOM SEED= 551699426

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.260
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.260
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:       1823720 kB
Buffers:         34792 kB
Cached:          87496 kB
SwapCached:       9904 kB
Active:         115920 kB
Inactive:        60048 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1823720 kB
SwapTotal:     4192956 kB
SwapFree:      4171244 kB
Dirty:            3180 kB
Writeback:           0 kB
Mapped:          64284 kB
Slab:            40976 kB
Committed_AS:  4530800 kB
PageTables:       2388 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= 66318 MiB



End job on node19 on Mon Jan  8 10:57:13 UTC 2007