Trace number 39406

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 6.96794 7.00715

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
prestwich/armies/normalized-army11.17bt.opb
MD5SUMbde651356fbc7760944c2b16aa27f15d
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 benchmark4.34734
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables370
Total number of constraints809
Number of constraints which are clauses558
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints249
Minimum length of a constraint1
Maximum length of a constraint121
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 17
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 138
Number of bits of the biggest sum of numbers8
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.03	c INFO: OSL Context initialized.
0.06	c Initial problem consists of 370 variables and 809 constraints.
0.06	c Using non-optimization problem switches.
0.06	c No problem reductions applied in OPT. instance.
0.06	c	preprocess terminated. Elapsed time: 0.027
0.06	c After prepocess the problem consists of 354 variables and 776 constraints.
0.10	c Restart #1 #Var: 353 LB: 0 @ 0.064
0.16	c Restart #2 #Var: 353 LB: 0 @ 0.124
0.25	c Restart #3 #Var: 353 LB: 0 @ 0.218
0.39	c Restart #4 #Var: 353 LB: 0 @ 0.354
0.54	c Restart #5 #Var: 352 LB: 0 @ 0.511
0.75	c Restart #6 #Var: 351 LB: 0 @ 0.715
0.99	c Restart #7 #Var: 351 LB: 0 @ 0.958
1.26	c Restart #8 #Var: 350 LB: 0 @ 1.227
1.56	c Restart #9 #Var: 350 LB: 0 @ 1.526
1.88	c Restart #10 #Var: 350 LB: 0 @ 1.847
2.25	c Restart #11 #Var: 350 LB: 0 @ 2.219
2.63	c Restart #12 #Var: 348 LB: 0 @ 2.594
3.09	c Restart #13 #Var: 348 LB: 0 @ 3.057
3.61	c Restart #14 #Var: 348 LB: 0 @ 3.572
4.11	c Restart #15 #Var: 348 LB: 0 @ 4.08
4.64	c Restart #16 #Var: 348 LB: 0 @ 4.606
5.21	c Restart #17 #Var: 348 LB: 0 @ 5.176
5.83	c Restart #18 #Var: 348 LB: 0 @ 5.793
6.54	c Restart #19 #Var: 348 LB: 0 @ 6.51
7.00	c Sol. found (all assignments made)...
7.00	o 0
7.00	c NEW SOLUTION FOUND: 0 @ 6.964
7.00	s SATISFIABLE
7.00	c Cost: 0
7.00	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
7.00	v -x57 -x59 x61 -x63 x65 -x67 -x69 -x71 -x73 -x75 -x77 -x79 -x81 -x83 -x85 -x87 -x89 -x91 -x93 -x95 -x97 -x99 -x101 -x103 -x105
7.00	v -x107 -x109 -x111 -x113 -x115 -x117 -x119 -x121 -x123 -x125 -x127 -x129 -x131 -x133 -x135 -x137 -x139 -x141 -x143 -x145 -x147
7.00	v -x149 -x151 -x153 -x155 -x157 -x159 -x161 -x163 -x165 -x167 -x169 -x171 -x173 -x175 x177 -x179 x181 -x183 -x185 -x187 -x189
7.00	v -x191 x193 x195 x197 -x199 -x201 -x203 -x205 -x207 -x209 -x211 -x213 -x215 -x217 -x219 x221 -x223 x225 -x227 -x229 -x231 -x233
7.00	v -x235 x237 -x239 x241 -x2 -x4 -x6 -x8 -x10 -x12 -x14 -x16 -x18 -x20 -x22 -x24 -x26 -x28 -x30 x32 x34 x36 -x38 -x40 -x42 -x44 -x46
7.00	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
7.00	v -x100 -x102 x104 -x106 -x108 -x110 -x112 x114 -x116 -x118 x120 -x122 -x124 -x126 -x128 -x130 -x132 -x134 x136 -x138 x140 -x142
7.00	v x144 -x146 -x148 -x150 -x152 -x154 -x156 -x158 -x160 -x162 x164 -x166 x168 -x170 -x172 -x174 -x176 -x178 -x180 -x182 -x184
7.00	v -x186 -x188 -x190 -x192 -x194 -x196 -x198 -x200 -x202 -x204 -x206 x208 x210 x212 -x214 -x216 -x218 -x220 -x222 -x224 -x226
7.00	v -x228 -x230 -x232 -x234 -x236 -x238 -x240 -x242 x244 -x243 -x246 x245 x248 -x247 -x250 x249 -x252 x251 -x254 x253 -x256 x255
7.00	v -x258 x257 x260 -x259 -x262 x261 x264 -x263 x266 -x265 -x268 x267 x270 -x269 -x272 x271 -x274 x273 -x276 x275 -x278 x277 -x280
7.00	v x279 x282 -x281 x284 -x283 x286 -x285 x288 -x287 -x290 x289 x292 -x291 -x294 x293 -x296 x295 -x298 x297 x300 -x299 -x302 -x301
7.00	v x304 -x303 -x306 -x305 x308 -x307 x310 -x309 -x312 -x311 x314 -x313 -x316 -x315 x318 -x317 -x320 x319 -x322 x321 -x324 x323
7.00	v x326 -x325 -x328 x327 x330 -x329 -x332 x331 x334 -x333 -x336 x335 -x338 x337 -x340 x339 x342 -x341 x344 -x343 x346 -x345 -x348
7.00	v -x347 x350 -x349 x352 -x351 -x354 -x353 x356 -x355 -x358 -x357 x360 -x359 -x362 x361 -x364 x363 -x366 x365 x368 -x367 x370
7.00	v -x369
7.00	c Exit Code: 10
7.00	c Total time: 6.964 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/node54/watcher-39406-1149204820 -o ROOT/results/node54/solver-39406-1149204820 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node54/39406-1149204820/instance-39406-1149204820.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.00 0.01 0.17 2/64 15624
/proc/meminfo: memFree=1328376/2055920 swapFree=4180872/4192956
[pid=15624] ppid=15622 vsize=4664 CPUtime=0
/proc/15624/stat : 15624 (bsolo) R 15622 15624 15579 0 -1 0 155 0 0 0 0 0 0 0 18 0 1 0 186149597 4775936 135 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 10095892 0 0 4096 0 0 0 0 17 1 0 0
/proc/15624/statm: 1166 136 106 55 0 46 0

Child status: 10
Real time (s): 7.00715
CPU time (s): 6.96794
CPU user time (s): 6.93994
CPU system time (s): 0.027995
CPU usage (%): 99.4404
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node54 on Thu Jun  1 23:33:41 UTC 2006


FILE ID= 39406-1149204820

PBS_JOBID= 293028

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  bde651356fbc7760944c2b16aa27f15d

RANDOM SEED= 504528895


/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.279
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.279
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:       1328776 kB
Buffers:         39236 kB
Cached:         611424 kB
SwapCached:       4180 kB
Active:         346756 kB
Inactive:       313048 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1328776 kB
SwapTotal:     4192956 kB
SwapFree:      4180872 kB
Dirty:             284 kB
Writeback:           0 kB
Mapped:          14908 kB
Slab:            53460 kB
Committed_AS:   180880 kB
PageTables:       1432 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node54 on Thu Jun  1 23:33:48 UTC 2006