Trace number 2657829

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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 3.2 ClSAT 0.009997 0.00966896

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga15_13_sat_pb.cnf.cr.opb
MD5SUM5525732a92b9529feed86b3ca7f3367f
Bench CategoryDEC-SMALLINT (no optimisation, small integers)
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.004998
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables293
Total number of constraints236
Number of constraints which are clauses208
Number of constraints which are cardinality constraints (but not clauses)28
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint7
Maximum length of a constraint15
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 16
Number of bits of the biggest sum of numbers5
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.00/0.00	c bsolo beta version 3.2 - 23/05/2010 : 1630 GMT
0.00/0.00	c Developed by Vasco Manquinho and José Santos IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Learning Strategy: Clause Learning
0.00/0.00	c Instance file HOME/instance-2657829-1276323035.opb
0.00/0.00	c File size is 17213 bytes.
0.00/0.00	c Highest Coefficient sum: 16
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0.002 s
0.00/0.00	c Var: 293 Constr: 236 208/28/0 Lit: 1957 Watch. Lit: 709
0.00/0.00	c Obj. Vars: 0 (0 % of total variables)
0.00/0.00	c Pre-processing Time: 0.007 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0    293      236     1957    8      709    1063      0      0 0.01
0.00/0.00	c Switching off lower bounding mode.
0.00/0.00	c Backtracks by Clause: 0
0.00/0.00	c Backtracks by PB constraint: 0
0.00/0.00	v -x22 -x232 -x233 -x234 -x235 -x236 x237 -x67 -x145 -x252 -x253 -x254 -x255 x256 -x257 -x258 -x32 -x202 -x203 -x204 -x205 x206 -x207 -x2 x65 -x220 -x221 -x222 x223 -x224 -x225 -x177 -x266 -x267 -x268 -x269 -x270 x271 -x272 x9 -x245 -x246 -x247 -x248 -x249 -x250 x251 x77 x158 -x238 -x239 -x240 x241 -x242 -x243 -x244 -x106 -x196 x197 -x198 -x199 -x200 -x201 -x15 -x287 -x288 x289 -x290 -x291 -x292 -x293 x115 -x51 -x226 -x227 x228 -x229 -x230 -x231 -x87 -x185 x172 x21 x131 -x259 x260 -x261 -x262 -x263 -x264 -x265 -x98 -x134 x280 -x281 -x282 -x283 -x284 -x285 -x286 -x58 -x273 -x274 -x275 -x276 -x277 -x278 -x279 x91 -x3 x208 -x209 -x210 -x211 -x212 -x213 -x140 -x112 -x52 -x133 x192 -x142 x33 x149 -x103 -x104 -x82 -x13 -x55 -x95 -x10 -x110 -x109 -x214 -x215 -x216 -x217 -x218 -x219 -x83 -x117 -x121 -x122 -x123 -x124 -x125 -x126 -x127 -x128 -x129 -x130 -x132 -x135 -x19 x60 -x107 -x108 -x111 -x113 -x114 -x116 -x118 -x119 -x120 -x188 -x59 -x150 -x138 -x71 -x61 -x62 -x63 -x64 -x66 -x68 -x69 -x70 -x72 -x73 -x74 -x75 -x147 -x180 -x20 -x181 -x182 -x183 -x184 -x186 -x187 -x189 -x190 -x191 -x193 -x194 -x195 -x50 -x90 -x17 -x46 -x161 -x97 -x1 -x4 -x5 -x6 -x7 -x8 -x11 -x12 -x14 -x92 -x152 -x44 -x85 -x89 -x86 -x164 -x170 -x171 -x169 -x16 -x173 -x159 -x84 -x37 -x29 -x174 -x23 -x136 -x163 -x144 -x28 -x48 -x178 -x24 -x148 -x26 -x56 -x18 -x25 -x27 -x30 -x47 -x162 -x99 -x96 -x41 -x42 -x151 -x153 -x154 -x155 -x156 -x157 -x160 -x165 -x176 -x57 -x93 -x94 -x100 -x101 -x102 -x105 -x38 -x43 -x166 -x167 -x168 -x175 -x179 -x39 -x49 -x76 -x79 -x31 -x35 -x40 -x36 -x54 -x78 -x80 -x88 -x143 -x45 -x81 -x139 -x53 -x137 -x146 -x34 -x141 
0.00/0.01	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.01	c    0        4      2      280      240     2142      4    500 0.01
0.00/0.01	s SATISFIABLE
0.00/0.01	c Total time: 0.008 s

Verifier Data 

OK	0

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2657829-1276323035/watcher-2657829-1276323035 -o /tmp/evaluation-result-2657829-1276323035/solver-2657829-1276323035 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l1 HOME/instance-2657829-1276323035.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.09 1.03 1.13 3/106 12995
/proc/meminfo: memFree=1953904/2059040 swapFree=4135100/4192956
[pid=12995] ppid=12993 vsize=10788 CPUtime=0
/proc/12995/stat : 12995 (bsolo_pb10) R 12993 12995 12220 0 -1 4202496 340 0 0 0 0 0 0 0 22 0 1 0 7905095 11046912 254 1992294400 134512640 137138936 4288235152 18446744073709551615 136570369 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/12995/statm: 2697 254 185 642 0 2053 0

Solver just ended. Dumping a history of the last processes samples

Child status: 0
Real time (s): 0.00966896
CPU time (s): 0.009997
CPU user time (s): 0.007998
CPU system time (s): 0.001999
CPU usage (%): 103.393
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.007998
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 347
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 1
involuntary context switches= 1

runsolver used 0.000999 second user time and 0.011998 second system time

The end

Launcher Data 

Begin job on node011 at 2010-06-12 08:10:35
IDJOB=2657829
IDBENCH=1406
IDSOLVER=1163
FILE ID=node011/2657829-1276323035
PBS_JOBID= 11173152
Free space on /tmp= 62264 MiB

SOLVER NAME= bsolo 3.2 Cl
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-fpga15_13_sat_pb.cnf.cr.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l1 BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2657829-1276323035/watcher-2657829-1276323035 -o /tmp/evaluation-result-2657829-1276323035/solver-2657829-1276323035 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l1 HOME/instance-2657829-1276323035.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 5525732a92b9529feed86b3ca7f3367f
RANDOM SEED=1590071520

node011.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.264
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.52
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.264
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.45
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1954432 kB
Buffers:          4364 kB
Cached:          44124 kB
SwapCached:       7272 kB
Active:          40380 kB
Inactive:        16784 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1954432 kB
SwapTotal:     4192956 kB
SwapFree:      4135100 kB
Dirty:            4064 kB
Writeback:           0 kB
AnonPages:        7700 kB
Mapped:           6356 kB
Slab:            25748 kB
PageTables:       4016 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180056 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62260 MiB
End job on node011 at 2010-06-12 08:10:35