Trace number 39410

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 0.239963 0.272668

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
prestwich/armies/normalized-army8.9ls.opb
MD5SUMf22ee27ae396dfbceb6d2e4359af424f
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 benchmark0.053991
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables220
Total number of constraints332
Number of constraints which are clauses202
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints128
Minimum length of a constraint2
Maximum length of a constraint64
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 9
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 73
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.03	c INFO: OSL Context initialized.
0.04	c Initial problem consists of 220 variables and 332 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.012
0.04	c After prepocess the problem consists of 220 variables and 332 constraints.
0.06	c Restart #1 #Var: 220 LB: 0 @ 0.032
0.11	c Restart #2 #Var: 220 LB: 0 @ 0.081
0.18	c Restart #3 #Var: 220 LB: 0 @ 0.149
0.27	c Sol. found (all assignments made)...
0.27	o 0
0.27	c NEW SOLUTION FOUND: 0 @ 0.236
0.27	s SATISFIABLE
0.27	c Cost: 0
0.27	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
0.27	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
0.27	v -x107 -x109 x111 -x113 -x115 -x117 x119 x121 x123 -x125 -x127 x2 -x4 x6 -x8 -x10 -x12 x14 -x16 x18 x20 -x22 -x24 -x26 -x28 x30
0.27	v -x32 -x34 x36 x38 -x40 -x42 -x44 -x46 -x48 -x50 -x52 -x54 -x56 -x58 -x60 -x62 -x64 -x66 -x68 -x70 -x72 -x74 -x76 -x78 -x80 x82
0.27	v -x84 -x86 -x88 -x90 -x92 -x94 -x96 -x98 -x100 -x102 -x104 -x106 -x108 -x110 -x112 -x114 -x116 -x118 -x120 -x122 -x124 -x126
0.27	v -x128 -x130 x129 -x132 x131 -x134 x133 x136 -x135 x138 -x137 -x140 x139 x142 -x141 x144 -x143 -x146 x145 -x148 x147 -x150 x149
0.27	v x152 -x151 x154 -x153 x156 -x155 -x158 x157 x160 -x159 -x162 x161 -x164 x163 x166 -x165 x168 -x167 x170 -x169 -x172 x171 -x174
0.27	v -x173 -x176 -x175 -x178 x177 -x180 x179 -x182 x181 -x184 x183 -x186 x185 -x188 x187 -x190 x189 -x192 x191 -x194 -x193 x196
0.27	v -x195 x198 -x197 x200 -x199 x202 -x201 x204 -x203 -x206 -x205 -x208 -x207 -x210 x209 -x212 x211 x214 -x213 x216 -x215 -x218
0.27	v x217 x220 -x219
0.27	c Exit Code: 10
0.27	c Total time: 0.236 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/node29/watcher-39410-1149204922 -o ROOT/results/node29/solver-39410-1149204922 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node29/39410-1149204922/instance-39410-1149204922.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.75 0.69 0.96 2/64 3026
/proc/meminfo: memFree=1121560/2055920 swapFree=4181384/4192956
[pid=3026] ppid=3024 vsize=2900 CPUtime=0
/proc/3026/stat : 3026 (bsolo) D 3024 3026 2981 0 -1 0 43 0 0 0 0 0 0 0 18 0 1 0 186155822 2969600 27 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4129572 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/3026/statm: 725 27 19 55 0 38 0

Child status: 10
Real time (s): 0.272668
CPU time (s): 0.239963
CPU user time (s): 0.233964
CPU system time (s): 0.005999
CPU usage (%): 88.0056
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node29 on Thu Jun  1 23:35:22 UTC 2006


FILE ID= 39410-1149204922

PBS_JOBID= 293078

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  f22ee27ae396dfbceb6d2e4359af424f

RANDOM SEED= 640973679


/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.259
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.259
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:       1121768 kB
Buffers:         47668 kB
Cached:         803360 kB
SwapCached:       3392 kB
Active:         343244 kB
Inactive:       516572 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1121768 kB
SwapTotal:     4192956 kB
SwapFree:      4181384 kB
Dirty:             256 kB
Writeback:           0 kB
Mapped:          14700 kB
Slab:            60320 kB
Committed_AS:   185460 kB
PageTables:       1504 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node29 on Thu Jun  1 23:35:23 UTC 2006