Trace number 191955

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 1.06284 1.07839

General information on the benchmark

Namequeens/
queens-150.xml
MD5SUMb0d89abe262117e726883b3c610dd5a5
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark1.06284
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables150
Number of constraints11175
Maximum constraint arity2
Maximum domain size150
Number of constraints which are defined in extension0
Number of constraints which are defined in intension11175
Global constraints used (with number of constraints)

Solver Data (download as text)

0.20	c 
0.20	c Parsing xml file
0.20	c 	domains...............    0
0.20	c 	variables.............    0
0.20	c 	predicates............    0
0.20	c 	constraints........... 0.74
0.76	c Allocating memory
0.76	c 
0.76	c time limit = -1
0.76	c heuristic = dom/wdeg
0.76	c restart policy = No restart
0.76	c 
0.76	c Solving
0.76	c
1.06	s SATISFIABLE
1.06	v 1 3 5 69 73 4 64 7 145 90 123 68 6 63 66 98 8 78 65 67 47 61 9 62 87 81 86 121 127 10 122 59 56 97 50 70 91 11 71 54 89 79 83 75 52 74 12 149 41 128 126 147 120 150 100 20 13 144 42 39 55 49 72 53 40 99 21 14 77 94 129 142 45 143 141 137 48 82 96 15 134 85 46 95 103 22 109 140 130 102 112 80 16 113 115 146 132 88 135 2 35 118 133 43 37 148 17 60 138 29 107 93 108 139 125 58 76 131 124 117 105 18 27 57 110 26 24 31 34 136 101 92 111 28 104 25 114 19 30 106 84 116 119 32 38 44 33 23 36 51
1.06	d          SAT         0 BTS      0.28 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/node17/watcher-191955-1168096421 -o ROOT/results/node17/solver-191955-1168096421 -C 1800 -M 900 /tmp/evaluation/191955-1168096421/mistral/bin/solver /tmp/evaluation/191955-1168096421/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.00 1.18 1.51 5/86 20111
/proc/meminfo: memFree=1503720/2055920 swapFree=4192812/4192956
[pid=20110] ppid=20108 vsize=540 CPUtime=0
/proc/20110/stat : 20110 (solver) R 20108 20110 19866 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 158038139 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 2859812 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/20110/statm: 135 26 21 92 0 18 0

[startup+0.103811 s]
/proc/loadavg: 1.00 1.18 1.51 5/86 20111
/proc/meminfo: memFree=1503720/2055920 swapFree=4192812/4192956
[pid=20110] ppid=20108 vsize=7452 CPUtime=0.09
/proc/20110/stat : 20110 (solver) R 20108 20110 19866 0 -1 4194304 946 0 0 0 9 0 0 0 18 0 1 0 158038139 7630848 914 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 3292817 0 0 4096 0 0 0 0 17 1 0 0
/proc/20110/statm: 1863 914 706 92 0 207 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7452

[startup+0.511851 s]
/proc/loadavg: 1.00 1.18 1.51 5/86 20111
/proc/meminfo: memFree=1503720/2055920 swapFree=4192812/4192956
[pid=20110] ppid=20108 vsize=9168 CPUtime=0.49
/proc/20110/stat : 20110 (solver) R 20108 20110 19866 0 -1 4194304 1365 0 0 0 49 0 0 0 21 0 1 0 158038139 9388032 1333 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 3292592 0 0 4096 0 0 0 0 17 1 0 0
/proc/20110/statm: 2292 1333 706 92 0 636 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 9168

Child status: 0
Real time (s): 1.07839
CPU time (s): 1.06284
CPU user time (s): 1.05084
CPU system time (s): 0.011998
CPU usage (%): 98.5579
Max. virtual memory (cumulated for all children) (KiB): 11356

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.05084
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1908
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= 44

runsolver used 0.002999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node17 on Sat Jan  6 15:13:48 UTC 2007


IDJOB= 191955
IDBENCH= 3081
FILE ID= node17/191955-1168096421

PBS_JOBID= 3476487

Free space on /tmp= 66316 MiB

BENCH NAME= HOME/pub/bench/CPAI06/queens/queens-150.xml
COMMAND LINE= /tmp/evaluation/191955-1168096421/mistral/bin/solver /tmp/evaluation/191955-1168096421/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-191955-1168096421 -o ROOT/results/node17/solver-191955-1168096421 -C 1800 -M 900  /tmp/evaluation/191955-1168096421/mistral/bin/solver /tmp/evaluation/191955-1168096421/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  b0d89abe262117e726883b3c610dd5a5

RANDOM SEED= 383053855

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:       1504328 kB
Buffers:         40240 kB
Cached:         271676 kB
SwapCached:          0 kB
Active:         272764 kB
Inactive:       187488 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1504328 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            4640 kB
Writeback:           0 kB
Mapped:         170840 kB
Slab:            76124 kB
Committed_AS:  4012208 kB
PageTables:       2384 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= 66316 MiB



End job on node17 on Sat Jan  6 15:13:57 UTC 2007