Trace number 39405

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
bsolo 2006/05SAT 18.5122 18.5356

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
prestwich/armies/normalized-army10.14bt.opb
MD5SUM35996461279b46395c12d24fd378138e
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark1.46578
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables316
Total number of constraints686
Number of constraints which are clauses477
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints207
Minimum length of a constraint1
Maximum length of a constraint100
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 16
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 114
Number of bits of the biggest sum of numbers7
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00	c Time Limit set via PBTIMEOUT to 1800
0.02	c INFO: OSL Context initialized.
0.04	c Initial problem consists of 316 variables and 686 constraints.
0.04	c Using non-optimization problem switches.
0.04	c No problem reductions applied in OPT. instance.
0.04	c	preprocess terminated. Elapsed time: 0.025
0.04	c After prepocess the problem consists of 301 variables and 655 constraints.
0.07	c Restart #1 #Var: 299 LB: 0 @ 0.057
0.14	c Restart #2 #Var: 299 LB: 0 @ 0.125
0.23	c Restart #3 #Var: 299 LB: 0 @ 0.219
0.39	c Restart #4 #Var: 299 LB: 0 @ 0.378
0.57	c Restart #5 #Var: 298 LB: 0 @ 0.556
0.76	c Restart #6 #Var: 298 LB: 0 @ 0.742
1.07	c Restart #7 #Var: 298 LB: 0 @ 1.055
1.44	c Restart #8 #Var: 298 LB: 0 @ 1.428
1.85	c Restart #9 #Var: 298 LB: 0 @ 1.833
2.37	c Restart #10 #Var: 297 LB: 0 @ 2.354
2.96	c Restart #11 #Var: 297 LB: 0 @ 2.947
3.55	c Restart #12 #Var: 295 LB: 0 @ 3.537
4.51	c Restart #13 #Var: 295 LB: 0 @ 4.492
5.18	c Restart #14 #Var: 295 LB: 0 @ 5.163
6.13	c Restart #15 #Var: 295 LB: 0 @ 6.117
7.46	c Restart #16 #Var: 295 LB: 0 @ 7.45
9.71	c Restart #17 #Var: 295 LB: 0 @ 9.696
11.57	c Restart #18 #Var: 295 LB: 0 @ 11.552
13.32	c Restart #19 #Var: 295 LB: 0 @ 13.301
15.83	c Restart #20 #Var: 295 LB: 0 @ 15.81
18.52	c Sol. found (all assignments made)...
18.52	o 0
18.52	c NEW SOLUTION FOUND: 0 @ 18.504
18.52	s SATISFIABLE
18.52	c Cost: 0
18.52	v x1 -x3 -x5 -x7 -x9 x11 x13 -x15 -x17 -x19 x21 x23 -x25 -x27 -x29 x31 x33 -x35 -x37 -x39 -x41 x43 -x45 -x47 -x49 -x51 x53 -x55 -x57
18.52	v -x59 x61 -x63 -x65 x67 -x69 -x71 -x73 -x75 -x77 -x79 x81 x83 -x85 x87 -x89 -x91 -x93 -x95 -x97 -x99 -x101 -x103 -x105 -x107 -x109
18.52	v -x111 -x113 -x115 -x117 -x119 -x121 -x123 -x125 -x127 -x129 -x131 -x133 -x135 -x137 -x139 -x141 -x143 -x145 -x147 -x149 -x151
18.52	v -x153 -x155 -x157 -x159 -x161 -x163 -x165 -x167 -x169 -x171 -x173 -x175 -x177 -x179 -x181 -x183 -x185 -x187 -x189 -x191 -x193
18.52	v -x195 -x197 -x199 -x2 -x4 -x6 -x8 -x10 -x12 -x14 -x16 -x18 -x20 -x22 -x24 -x26 -x28 -x30 -x32 -x34 -x36 -x38 -x40 -x42 -x44 -x46
18.52	v -x48 -x50 -x52 -x54 -x56 -x58 -x60 -x62 -x64 -x66 -x68 -x70 -x72 -x74 -x76 -x78 -x80 -x82 -x84 -x86 -x88 -x90 -x92 -x94 -x96 -x98
18.52	v -x100 -x102 -x104 -x106 -x108 -x110 -x112 -x114 x116 x118 -x120 -x122 -x124 -x126 -x128 x130 -x132 -x134 x136 x138 x140 -x142
18.52	v -x144 x146 -x148 -x150 -x152 -x154 -x156 x158 x160 -x162 -x164 x166 -x168 -x170 -x172 -x174 -x176 -x178 x180 -x182 -x184 x186
18.52	v -x188 x190 -x192 -x194 x196 -x198 -x200 x202 -x201 x204 -x203 x206 -x205 x208 -x207 x210 -x209 -x212 x211 -x214 x213 -x216
18.52	v x215 -x218 x217 -x220 x219 x222 -x221 x224 -x223 -x226 x225 x228 -x227 -x230 x229 x232 -x231 x234 -x233 -x236 x235 -x238 x237
18.52	v -x240 x239 x242 -x241 x244 -x243 -x246 x245 x248 -x247 x250 -x249 -x252 x251 -x254 x253 -x256 x255 -x258 -x257 -x260 -x259
18.52	v x262 -x261 x264 -x263 x266 -x265 x268 -x267 x270 -x269 x272 -x271 x274 -x273 x276 -x275 x278 -x277 -x280 x279 -x282 x281 -x284
18.52	v x283 -x286 x285 -x288 x287 -x290 x289 -x292 x291 -x294 x293 -x296 x295 -x298 -x297 -x300 -x299 -x302 -x301 -x304 -x303 x306
18.52	v -x305 x308 -x307 x310 -x309 -x312 x311 -x314 x313 -x316 x315
18.52	c Exit Code: 10
18.52	c Total time: 18.504 s

Verifier Data (download as text)

OK	0

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node56/watcher-39405-1149204819 -o ROOT/results/node56/solver-39405-1149204819 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node56/39405-1149204819/instance-39405-1149204819.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.08 0.04 0.18 2/64 4749
/proc/meminfo: memFree=1223176/2055920 swapFree=4181332/4192956
[pid=4749] ppid=4747 vsize=2900 CPUtime=0
/proc/4749/stat : 4749 (bsolo) R 4747 4749 4704 0 -1 0 43 0 0 0 0 0 0 0 18 0 1 0 186149588 2969600 27 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 10027812 0 0 4096 0 0 0 0 17 1 0 0
/proc/4749/statm: 725 27 19 55 0 38 0

[startup+10.0013 s]
/proc/loadavg: 0.22 0.07 0.19 2/64 4749
/proc/meminfo: memFree=1199112/2055920 swapFree=4181332/4192956
[pid=4749] ppid=4747 vsize=28648 CPUtime=9.98
/proc/4749/stat : 4749 (bsolo) R 4747 4749 4704 0 -1 0 6428 0 0 0 991 7 0 0 25 0 1 0 186149588 29335552 6343 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4749/statm: 7162 6343 300 55 0 6054 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 28648

Child status: 10
Real time (s): 18.5356
CPU time (s): 18.5122
CPU user time (s): 18.4052
CPU system time (s): 0.106983
CPU usage (%): 99.8738
Max. virtual memory (cumulated for all children) (Kb): 28648

Launcher Data (download as text)

Begin job on node56 on Thu Jun  1 23:33:40 UTC 2006


FILE ID= 39405-1149204819

PBS_JOBID= 293014

BENCH NAME= ROOT/tmp/node56/39405-1149204819/instance-39405-1149204819.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node56/39405-1149204819/instance-39405-1149204819.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node56/watcher-39405-1149204819 -o ROOT/results/node56/solver-39405-1149204819 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node56/39405-1149204819/instance-39405-1149204819.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  35996461279b46395c12d24fd378138e

RANDOM SEED= 847400566


/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.232
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.232
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:       1223576 kB
Buffers:         39800 kB
Cached:         714480 kB
SwapCached:       3648 kB
Active:         276308 kB
Inactive:       487032 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1223576 kB
SwapTotal:     4192956 kB
SwapFree:      4181332 kB
Dirty:             272 kB
Writeback:           0 kB
Mapped:          14900 kB
Slab:            55000 kB
Committed_AS:   160172 kB
PageTables:       1496 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node56 on Thu Jun  1 23:33:59 UTC 2006