Trace number 200468

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-04UNSAT 18.0523 18.2154

General information on the benchmark

NamequeensKnights/
queensKnights-10-5-mul.xml
MD5SUMcbc258ed026c4b607de8e359683e6583
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.382941
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables15
Number of constraints105
Maximum constraint arity2
Maximum domain size100
Number of constraints which are defined in extension0
Number of constraints which are defined in intension105
Global constraints used (with number of constraints)

Solver Data (download as text)

0.11	c 
0.11	c Parsing xml file
0.11	c 	domains...............    0
0.11	c 	variables.............    0
0.11	c 	predicates............    0
0.11	c 	constraints...........    0
0.11	c Allocating memory
0.11	c 
0.11	c time limit = -1
0.11	c heuristic = dom/wdeg
0.11	c restart policy = No restart
0.11	c 
0.11	c Solving
0.11	c
18.21	s UNSATISFIABLE
18.21	d        UNSAT      7490 BTS        18 s

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node9/watcher-200468-1168142727 -o ROOT/results/node9/solver-200468-1168142727 -C 1800 -M 900 /tmp/evaluation/200468-1168142727/mistral/bin/solver /tmp/evaluation/200468-1168142727/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: 2.39 2.22 2.11 5/93 9259
/proc/meminfo: memFree=1765248/2055920 swapFree=4191880/4192956
[pid=9258] ppid=9256 vsize=4552 CPUtime=0
/proc/9258/stat : 9258 (solver) D 9256 9258 9014 0 -1 4194304 54 0 0 0 0 0 0 0 20 0 1 0 162667976 4661248 38 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8663844 0 0 4096 0 18446744071563608240 0 0 17 1 0 0
/proc/9258/statm: 1138 38 30 92 0 19 0

[startup+0.10425 s]
/proc/loadavg: 2.39 2.22 2.11 5/93 9259
/proc/meminfo: memFree=1765248/2055920 swapFree=4191880/4192956
[pid=9258] ppid=9256 vsize=7312 CPUtime=0.09
/proc/9258/stat : 9258 (solver) R 9256 9258 9014 0 -1 4194304 906 0 0 0 9 0 0 0 20 0 1 0 162667976 7487488 874 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134711873 0 0 4096 0 0 0 0 17 1 0 0
/proc/9258/statm: 1828 874 719 92 0 172 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7312

[startup+0.512292 s]
/proc/loadavg: 2.39 2.22 2.11 5/93 9259
/proc/meminfo: memFree=1765248/2055920 swapFree=4191880/4192956
[pid=9258] ppid=9256 vsize=7316 CPUtime=0.5
/proc/9258/stat : 9258 (solver) R 9256 9258 9014 0 -1 4194304 907 0 0 0 50 0 0 0 25 0 1 0 162667976 7491584 875 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134637120 0 0 4096 0 0 0 0 17 1 0 0
/proc/9258/statm: 1829 875 719 92 0 173 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 7316

[startup+1.33338 s]
/proc/loadavg: 2.39 2.22 2.11 3/93 9259
/proc/meminfo: memFree=1764480/2055920 swapFree=4191880/4192956
[pid=9258] ppid=9256 vsize=7316 CPUtime=1.31
/proc/9258/stat : 9258 (solver) R 9256 9258 9014 0 -1 4194304 907 0 0 0 131 0 0 0 25 0 1 0 162667976 7491584 875 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134722033 0 0 4096 0 0 0 0 17 1 0 0
/proc/9258/statm: 1829 875 719 92 0 173 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 7316

[startup+2.97657 s]
/proc/loadavg: 2.39 2.22 2.11 3/93 9259
/proc/meminfo: memFree=1764480/2055920 swapFree=4191880/4192956
[pid=9258] ppid=9256 vsize=7316 CPUtime=2.94
/proc/9258/stat : 9258 (solver) R 9256 9258 9014 0 -1 4194304 907 0 0 0 294 0 0 0 25 0 1 0 162667976 7491584 875 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134712119 0 0 4096 0 0 0 0 17 1 0 0
/proc/9258/statm: 1829 875 719 92 0 173 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 7316

[startup+6.25494 s]
/proc/loadavg: 2.36 2.22 2.11 3/93 9259
/proc/meminfo: memFree=1764480/2055920 swapFree=4191880/4192956
[pid=9258] ppid=9256 vsize=7316 CPUtime=6.19
/proc/9258/stat : 9258 (solver) R 9256 9258 9014 0 -1 4194304 907 0 0 0 619 0 0 0 25 0 1 0 162667976 7491584 875 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134708945 0 0 4096 0 0 0 0 17 1 0 0
/proc/9258/statm: 1829 875 719 92 0 173 0
Current children cumulated CPU time (s) 6.19
Current children cumulated vsize (KiB) 7316

[startup+12.7157 s]
/proc/loadavg: 2.33 2.21 2.11 3/93 9259
/proc/meminfo: memFree=1764544/2055920 swapFree=4191880/4192956
[pid=9258] ppid=9256 vsize=7316 CPUtime=12.59
/proc/9258/stat : 9258 (solver) R 9256 9258 9014 0 -1 4194304 907 0 0 0 1259 0 0 0 25 0 1 0 162667976 7491584 875 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134710641 0 0 4096 0 0 0 0 17 1 0 0
/proc/9258/statm: 1829 875 719 92 0 173 0
Current children cumulated CPU time (s) 12.59
Current children cumulated vsize (KiB) 7316

Child status: 0
Real time (s): 18.2154
CPU time (s): 18.0523
CPU user time (s): 18.0493
CPU system time (s): 0.002999
CPU usage (%): 99.1043
Max. virtual memory (cumulated for all children) (KiB): 7316

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 18.0493
system time used= 0.002999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 919
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= 15
involuntary context switches= 802

runsolver used 0.015997 s user time and 0.055991 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Sun Jan  7 04:05:27 UTC 2007


IDJOB= 200468
IDBENCH= 3709
FILE ID= node9/200468-1168142727

PBS_JOBID= 3477847

Free space on /tmp= 66540 MiB

BENCH NAME= HOME/pub/bench/CPAI06/queensKnights/queensKnights-10-5-mul.xml
COMMAND LINE= /tmp/evaluation/200468-1168142727/mistral/bin/solver /tmp/evaluation/200468-1168142727/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-200468-1168142727 -o ROOT/results/node9/solver-200468-1168142727 -C 1800 -M 900  /tmp/evaluation/200468-1168142727/mistral/bin/solver /tmp/evaluation/200468-1168142727/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  cbc258ed026c4b607de8e359683e6583

RANDOM SEED= 884657984

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.231
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.231
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:       1765664 kB
Buffers:         10508 kB
Cached:          93528 kB
SwapCached:        276 kB
Active:         159852 kB
Inactive:        68024 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1765664 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3292 kB
Writeback:           0 kB
Mapped:         145620 kB
Slab:            46840 kB
Committed_AS:  5079220 kB
PageTables:       2492 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= 66540 MiB



End job on node9 on Sun Jan  7 04:05:47 UTC 2007