Trace number 37105

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
Pueblo 1.3SAT 23.2015 23.211

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 Pueblo version 1.4 (September 2005)
0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
0.01	c starting to Solve
0.01	c #variables read: 316 - #constraints read: 685
23.20	c total time              : 23.2 s
23.20	s SATISFIABLE
23.20	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
23.20	v -x55 -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 -x107
23.20	v -x109 x111 -x113 -x115 -x117 -x119 x121 -x123 -x125 -x127 x129 -x131 -x133 -x135 -x137 -x139 -x141 -x143 -x145 -x147 -x149
23.20	v -x151 -x153 -x155 -x157 -x159 -x161 -x163 -x165 -x167 -x169 -x171 -x173 -x175 -x177 -x179 -x181 x183 -x185 x187 -x189 x191
23.20	v -x193 -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
23.20	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
23.20	v -x100 -x102 -x104 -x106 -x108 -x110 -x112 -x114 -x116 -x118 -x120 -x122 -x124 -x126 -x128 -x130 -x132 -x134 -x136 -x138 -x140
23.20	v -x142 -x144 -x146 -x148 -x150 -x152 x154 -x156 x158 x160 -x162 -x164 -x166 -x168 -x170 -x172 -x174 x176 -x178 x180 -x182 -x184
23.20	v -x186 -x188 -x190 -x192 -x194 -x196 -x198 -x200 -x202 x201 -x204 x203 -x206 x205 x208 -x207 x210 -x209 x212 -x211 x214 -x213
23.20	v -x216 x215 -x218 x217 x220 -x219 x222 -x221 x224 -x223 x226 -x225 x228 -x227 x230 -x229 x232 -x231 -x234 x233 -x236 x235 -x238
23.20	v x237 -x240 x239 x242 -x241 -x244 x243 x246 -x245 x248 -x247 x250 -x249 x252 -x251 x254 -x253 -x256 -x255 x258 -x257 -x260 -x259
23.20	v -x262 -x261 -x264 -x263 -x266 -x265 x268 -x267 x270 -x269 x272 -x271 x274 -x273 -x276 x275 -x278 x277 -x280 x279 x282 -x281
23.20	v -x284 x283 x286 -x285 -x288 x287 x290 -x289 -x292 x291 -x294 x293 -x296 x295 -x298 -x297 -x300 x299 -x302 x301 -x304 x303 -x306
23.20	v x305 -x308 x307 -x310 x309 -x312 -x311 -x314 x313 -x316 x315

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/node50/watcher-37105-1149204820 -o ROOT/results/node50/solver-37105-1149204820 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node50/37105-1149204820/instance-37105-1149204820.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.00 0.01 0.18 2/64 26359
/proc/meminfo: memFree=1472288/2055920 swapFree=4181340/4192956
[pid=26359] ppid=26357 vsize=2288 CPUtime=0
/proc/26359/stat : 26359 (Pueblo13) R 26357 26359 26313 0 -1 4194304 221 0 0 0 0 0 0 0 18 0 1 0 186149163 2342912 192 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/26359/statm: 572 192 169 16 0 13 0

[startup+10.0025 s]
/proc/loadavg: 0.15 0.04 0.19 2/64 26359
/proc/meminfo: memFree=1471088/2055920 swapFree=4181340/4192956
[pid=26359] ppid=26357 vsize=3484 CPUtime=9.99
/proc/26359/stat : 26359 (Pueblo13) R 26357 26359 26313 0 -1 4194304 524 0 0 0 999 0 0 0 25 0 1 0 186149163 3567616 495 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 134528051 0 0 4096 0 0 0 0 17 1 0 0
/proc/26359/statm: 871 495 205 16 0 312 0
Current children cumulated CPU time (s) 9.99
Current children cumulated vsize (Kb) 3484

[startup+20.0093 s]
/proc/loadavg: 0.28 0.07 0.19 2/64 26359
/proc/meminfo: memFree=1470960/2055920 swapFree=4181340/4192956
[pid=26359] ppid=26357 vsize=3688 CPUtime=20
/proc/26359/stat : 26359 (Pueblo13) R 26357 26359 26313 0 -1 4194304 561 0 0 0 2000 0 0 0 25 0 1 0 186149163 3776512 532 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 134557272 0 0 4096 0 0 0 0 17 1 0 0
/proc/26359/statm: 922 532 205 16 0 363 0
Current children cumulated CPU time (s) 20
Current children cumulated vsize (Kb) 3688

Child status: 10
Real time (s): 23.211
CPU time (s): 23.2015
CPU user time (s): 23.1965
CPU system time (s): 0.004999
CPU usage (%): 99.9591
Max. virtual memory (cumulated for all children) (Kb): 3688

Launcher Data (download as text)

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


FILE ID= 37105-1149204820

PBS_JOBID= 293015

BENCH NAME= ROOT/tmp/node50/37105-1149204820/instance-37105-1149204820.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node50/37105-1149204820/instance-37105-1149204820.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node50/watcher-37105-1149204820 -o ROOT/results/node50/solver-37105-1149204820 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo13 ROOT/tmp/node50/37105-1149204820/instance-37105-1149204820.opb

MD5SUM SOLVER= b45add8200bccdf53727749bff226bd1
MD5SUM BENCH=  35996461279b46395c12d24fd378138e

RANDOM SEED= 818105135


/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.238
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.238
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:       1472496 kB
Buffers:         22780 kB
Cached:         488888 kB
SwapCached:       3432 kB
Active:          53216 kB
Inactive:       467436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1472496 kB
SwapTotal:     4192956 kB
SwapFree:      4181340 kB
Dirty:             268 kB
Writeback:           0 kB
Mapped:          14916 kB
Slab:            48732 kB
Committed_AS:   168736 kB
PageTables:       1480 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node50 on Thu Jun  1 23:34:03 UTC 2006