Trace number 37393

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 0.062989 0.068132

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga13_13_sat_pb.cnf.cr.opb
MD5SUMbf7e21954a6ae09c036e6d4bdde8af91
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.003998
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables254
Total number of constraints208
Number of constraints which are clauses182
Number of constraints which are cardinality constraints (but not clauses)26
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint6
Maximum length of a constraint13
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 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 14
Number of bits of the biggest sum of numbers4
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: 254 - #constraints read: 208
0.06	c total time              : 0.06 s
0.06	s SATISFIABLE
0.06	v -x115 -x234 -x235 -x236 -x237 -x238 -x239 x240 -x31 -x194 -x195 -x196 -x197 x198 -x199 -x24 -x1 x2 -x3 -x4 -x5 -x6 -x7 -x8 -x9
0.06	v -x10 -x11 -x12 -x13 -x83 -x87 -x220 -x221 -x222 -x223 -x224 x225 -x226 -x116 -x241 -x242 -x243 -x244 x245 -x246 -x247 -x123
0.06	v -x200 x201 -x202 -x203 -x204 -x205 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48 -x49 x50 -x51 -x52 -x132 x176 -x177 -x178 -x179
0.06	v -x180 -x181 -x33 -x206 -x207 -x208 x209 -x210 -x211 -x212 -x66 -x170 -x171 -x172 -x173 -x174 x175 -x36 -x227 x228 -x229 -x230
0.06	v -x231 -x232 -x233 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 x103 -x104 -x141 -x39 -x248 -x249 x250 -x251 -x252
0.06	v -x253 -x254 -x62 -x105 -x106 -x107 -x108 x109 -x110 -x111 -x112 -x113 -x114 -x117 -x61 -x64 -x125 x213 -x214 -x215 -x216 -x217
0.06	v -x218 -x219 -x38 -x150 -x60 -x27 -x28 -x29 -x30 x32 -x34 -x35 -x37 -x159 -x182 -x183 x184 -x185 -x186 -x187 -x86 -x25 -x16 -x155
0.06	v -x163 x85 -x133 -x54 -x161 -x19 -x160 -x188 -x189 -x190 x191 -x192 -x193 -x18 -x164 -x91 -x118 -x149 -x90 -x134 -x120 -x67
0.06	v -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 x78 -x166 -x58 -x126 -x145 -x153 -x143 x151 -x129 -x157 -x22 x140 -x130 -x139
0.06	v -x17 -x162 -x154 -x89 -x119 x121 -x122 -x124 -x127 -x128 -x144 -x152 -x142 -x23 x14 -x15 -x20 -x21 -x26 x55 -x81 -x63 -x147
0.06	v -x131 -x88 -x148 x165 -x135 -x167 -x138 -x146 -x53 -x56 -x57 -x59 -x65 -x169 -x137 -x168 -x79 -x136 -x82 -x80 -x84 -x156 -x158

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.78 0.94 0.90 3/64 13503
/proc/meminfo: memFree=873712/2055920 swapFree=4181356/4192956
[pid=13503] ppid=13501 vsize=2328 CPUtime=0
/proc/13503/stat : 13503 (Pueblo13) R 13501 13503 13458 0 -1 4194304 71 0 0 0 0 0 0 0 19 0 1 0 189113011 2383872 55 18446744073709551615 134512640 134579064 4294956672 18446744073709551615 7664915 0 0 4096 0 0 0 0 17 1 0 0
/proc/13503/statm: 582 68 53 16 0 11 0

Child status: 10
Real time (s): 0.068132
CPU time (s): 0.062989
CPU user time (s): 0.06099
CPU system time (s): 0.001999
CPU usage (%): 92.4514
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node34 on Fri Jun  2 07:48:12 UTC 2006


FILE ID= 37393-1149234492

PBS_JOBID= 296755

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

MD5SUM SOLVER= b45add8200bccdf53727749bff226bd1
MD5SUM BENCH=  bf7e21954a6ae09c036e6d4bdde8af91

RANDOM SEED= 107774554


/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.277
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.277
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:        873920 kB
Buffers:         38880 kB
Cached:        1068364 kB
SwapCached:       3536 kB
Active:          95084 kB
Inactive:      1021168 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        873920 kB
SwapTotal:     4192956 kB
SwapFree:      4181356 kB
Dirty:             280 kB
Writeback:           0 kB
Mapped:          14828 kB
Slab:            51816 kB
Committed_AS:   253564 kB
PageTables:       1416 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node34 on Fri Jun  2 07:48:12 UTC 2006