Trace number 199077

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 0.108983 0.117083

General information on the benchmark

Nameknights/
knights-8-5.xml
MD5SUM4005f912b0d8a06982611eb54b99e9e7
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.079987
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables5
Number of constraints10
Maximum constraint arity2
Maximum domain size64
Number of constraints which are defined in extension0
Number of constraints which are defined in intension10
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
0.11	s UNSATISFIABLE
0.11	d        UNSAT        94 BTS       0.1 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/node19/watcher-199077-1168132415 -o ROOT/results/node19/solver-199077-1168132415 -C 1800 -M 900 /tmp/evaluation/199077-1168132415/mistral/bin/solver /tmp/evaluation/199077-1168132415/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.78 1.96 1.95 5/89 8658
/proc/meminfo: memFree=1560368/2055920 swapFree=4171244/4192956
[pid=8657] ppid=8655 vsize=540 CPUtime=0
/proc/8657/stat : 8657 (solver) R 8655 8657 8202 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 161636348 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7484196 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/8657/statm: 135 26 21 92 0 18 0

[startup+0.105061 s]
/proc/loadavg: 1.78 1.96 1.95 5/89 8658
/proc/meminfo: memFree=1560368/2055920 swapFree=4171244/4192956
[pid=8657] ppid=8655 vsize=7048 CPUtime=0.09
/proc/8657/stat : 8657 (solver) R 8655 8657 8202 0 -1 4194304 837 0 0 0 9 0 0 0 18 0 1 0 161636348 7217152 805 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134709321 0 0 4096 0 0 0 0 17 1 0 0
/proc/8657/statm: 1762 805 713 92 0 106 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7048

Child status: 0
Real time (s): 0.117083
CPU time (s): 0.108983
CPU user time (s): 0.104984
CPU system time (s): 0.003999
CPU usage (%): 93.0818
Max. virtual memory (cumulated for all children) (KiB): 7048

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.104984
system time used= 0.003999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 850
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= 13
involuntary context switches= 3

runsolver used 0.002999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node19 on Sun Jan  7 01:13:37 UTC 2007


IDJOB= 199077
IDBENCH= 3591
FILE ID= node19/199077-1168132415

PBS_JOBID= 3477757

Free space on /tmp= 66309 MiB

BENCH NAME= HOME/pub/bench/CPAI06/knights/knights-8-5.xml
COMMAND LINE= /tmp/evaluation/199077-1168132415/mistral/bin/solver /tmp/evaluation/199077-1168132415/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node19/watcher-199077-1168132415 -o ROOT/results/node19/solver-199077-1168132415 -C 1800 -M 900  /tmp/evaluation/199077-1168132415/mistral/bin/solver /tmp/evaluation/199077-1168132415/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  4005f912b0d8a06982611eb54b99e9e7

RANDOM SEED= 793481809

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:       1560848 kB
Buffers:         56244 kB
Cached:         278960 kB
SwapCached:      10440 kB
Active:         174100 kB
Inactive:       259316 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1560848 kB
SwapTotal:     4192956 kB
SwapFree:      4171244 kB
Dirty:            3168 kB
Writeback:           0 kB
Mapped:         108348 kB
Slab:            46248 kB
Committed_AS:  4054568 kB
PageTables:       2584 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= 66309 MiB



End job on node19 on Sun Jan  7 01:13:38 UTC 2007