Trace number 222912

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-04SAT 0.346946 0.350532

General information on the benchmark

Namebqwh/bqwh-15-106/
bqwh-15-106-85_ext.xml
MD5SUMb269454eb143fab29a7718330c74e4d3
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.083986
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables106
Number of constraints644
Maximum constraint arity2
Maximum domain size6
Number of constraints which are defined in extension644
Number of constraints which are defined in intension0
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 	relations.............    0
0.02	c 	constraints........... 0.03
0.04	c Allocating memory
0.04	c 
0.04	c time limit = -1
0.04	c heuristic = dom/wdeg
0.04	c restart policy = Geometric increment
0.04	c restart base = 70
0.04	c restart factor = 1.33
0.04	c 
0.04	c Solving
0.04	c
0.34	s SATISFIABLE
0.34	v 7 9 4 0 1 8 14 7 8 6 12 11 13 3 12 6 8 5 7 3 4 14 1 3 12 6 9 13 14 10 8 11 2 0 5 0 2 14 9 3 8 5 5 12 7 3 4 8 6 0 3 4 8 14 7 9 5 14 10 6 7 1 0 11 10 5 4 2 12 0 9 4 1 3 7 12 0 6 0 7 12 14 13 2 6 1 10 7 13 4 5 13 11 5 6 14 1 3 10 3 2 6 4 0 11 1
0.34	d          SAT      4508 BTS       0.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/node60/watcher-222912-1168265053 -o ROOT/results/node60/solver-222912-1168265053 -C 1800 -M 900 /tmp/evaluation/222912-1168265053/tramontane/bin/solver /tmp/evaluation/222912-1168265053/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: 0.06 0.23 0.89 2/68 6611
/proc/meminfo: memFree=1742960/2055920 swapFree=4192812/4192956
[pid=6610] ppid=6608 vsize=6792 CPUtime=0
/proc/6610/stat : 6610 (solver) R 6608 6610 5610 0 -1 4194304 402 0 0 0 0 0 0 0 18 0 1 0 174904216 6955008 382 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 5502646 0 0 4096 0 0 0 0 17 1 0 0
/proc/6610/statm: 1698 389 357 92 0 30 0

[startup+0.103136 s]
/proc/loadavg: 0.06 0.23 0.89 2/68 6611
/proc/meminfo: memFree=1742960/2055920 swapFree=4192812/4192956
[pid=6610] ppid=6608 vsize=7576 CPUtime=0.09
/proc/6610/stat : 6610 (solver) R 6608 6610 5610 0 -1 4194304 968 0 0 0 9 0 0 0 18 0 1 0 174904216 7757824 936 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134727432 0 0 4096 0 0 0 0 17 1 0 0
/proc/6610/statm: 1894 936 712 92 0 238 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7576

Child status: 0
Real time (s): 0.350532
CPU time (s): 0.346946
CPU user time (s): 0.344947
CPU system time (s): 0.001999
CPU usage (%): 98.977
Max. virtual memory (cumulated for all children) (KiB): 7576

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

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node60 on Mon Jan  8 14:04:16 UTC 2007


IDJOB= 222912
IDBENCH= 5575
FILE ID= node60/222912-1168265053

PBS_JOBID= 3482738

Free space on /tmp= 66562 MiB

BENCH NAME= HOME/pub/bench/CPAI06/bqwh/bqwh-15-106/bqwh-15-106-85_ext.xml
COMMAND LINE= /tmp/evaluation/222912-1168265053/tramontane/bin/solver /tmp/evaluation/222912-1168265053/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node60/watcher-222912-1168265053 -o ROOT/results/node60/solver-222912-1168265053 -C 1800 -M 900  /tmp/evaluation/222912-1168265053/tramontane/bin/solver /tmp/evaluation/222912-1168265053/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  b269454eb143fab29a7718330c74e4d3

RANDOM SEED= 732501907

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.236
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.236
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:       1743536 kB
Buffers:         53492 kB
Cached:         182128 kB
SwapCached:          0 kB
Active:         141980 kB
Inactive:       113784 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1743536 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3080 kB
Writeback:           0 kB
Mapped:          30348 kB
Slab:            42372 kB
Committed_AS:  4217384 kB
PageTables:       1684 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= 66562 MiB



End job on node60 on Mon Jan  8 14:04:28 UTC 2007