Trace number 2657860

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.043993 0.0430151

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga12_11_sat_pb.cnf.cr.opb
MD5SUM05acc78c42ec3368f84785abcf0f7ebb
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.008998
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables198
Total number of constraints166
Number of constraints which are clauses143
Number of constraints which are cardinality constraints (but not clauses)23
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint6
Maximum length of a constraint12
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 13
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 

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-2657860-1276328886.opb
0.00/0.00	c File size is 10566 bytes.
0.00/0.00	c Highest Coefficient sum: 13
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0.001 s
0.00/0.00	c Var: 198 Constr: 166 143/23/0 Lit: 1188 Watch. Lit: 484
0.00/0.00	c Obj. Vars: 0 (0 % of total variables)
0.00/0.00	c Pre-processing Time: 0.004 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0    198      166     1188    7      484     597      0      0 0.00
0.00/0.00	c Switching off lower bounding mode.
0.00/0.04	c      100    198      266     3758   14      684     657    100  12500 0.01
0.00/0.04	c      250    198      416    11748   28      984     723    250  12500 0.02
0.00/0.04	c      475    198      641    25136   39     1434     796    475  11585 0.04
0.00/0.04	c Backtracks by Clause: 0
0.00/0.04	c Backtracks by PB constraint: 0
0.00/0.04	v -x76 -x148 -x149 -x150 -x151 -x152 x32 -x169 -x170 -x171 -x172 -x173 x174 -x85 -x133 -x134 -x135 -x136 x137 -x73 -x109 -x16 -x100 -x123 x143 -x144 -x145 -x146 -x147 -x110 -x111 -x112 -x113 -x114 x115 -x116 -x117 -x118 -x119 -x120 -x98 -x138 -x139 -x140 x141 -x142 -x61 -x57 x175 -x176 -x177 -x178 -x179 -x180 -x41 -x153 -x154 x155 -x156 -x157 -x63 x9 -x187 -x188 x189 -x190 -x191 -x192 -x8 -x26 -x45 -x37 -x68 -x72 -x193 -x194 -x195 -x196 x197 -x198 -x33 -x65 -x129 -x86 -x87 -x88 x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 x75 -x97 -x99 -x101 -x102 -x103 -x104 -x105 -x106 -x107 x108 -x62 -x64 -x66 -x67 -x69 -x70 x71 -x79 -x163 -x164 -x165 x166 -x167 -x168 -x14 -x20 -x125 x50 -x40 -x42 -x158 x159 -x160 -x161 -x162 -x60 -x19 -x49 -x51 -x52 -x53 -x54 -x55 -x56 -x58 -x59 -x1 -x12 -x21 -x35 -x78 -x13 x121 -x122 -x124 -x126 -x127 -x128 -x130 -x131 -x132 -x80 -x181 x182 -x183 -x184 -x185 -x186 -x38 -x15 -x4 -x44 -x74 -x23 -x6 -x77 -x43 -x84 -x7 -x47 -x34 -x17 -x25 -x27 -x28 -x29 -x30 -x31 -x36 -x11 -x3 x18 -x39 x46 -x48 -x81 -x82 -x83 -x10 -x2 -x5 -x22 -x24 
0.00/0.04	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.04	c    3      476    198     2280      642    25166    476  11333 0.04
0.00/0.04	s SATISFIABLE
0.00/0.04	c Total time: 0.042 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-2657860-1276328886/watcher-2657860-1276328886 -o /tmp/evaluation-result-2657860-1276328886/solver-2657860-1276328886 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l1 HOME/instance-2657860-1276328886.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.20 1.06 1.01 3/106 9829
/proc/meminfo: memFree=1851392/2059040 swapFree=4135896/4192956
[pid=9829] ppid=9827 vsize=10792 CPUtime=0
/proc/9829/stat : 9829 (bsolo_pb10) R 9827 9829 7191 0 -1 4202496 335 0 0 0 0 0 0 0 20 0 1 0 6544036 11051008 251 1992294400 134512640 137138936 4291390448 18446744073709551615 136570369 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/9829/statm: 2698 251 190 642 0 2054 0

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

Child status: 0
Real time (s): 0.0430151
CPU time (s): 0.043993
CPU user time (s): 0.038994
CPU system time (s): 0.004999
CPU usage (%): 102.273
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.038994
system time used= 0.004999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 419
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.002999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node026 at 2010-06-12 09:48:06
IDJOB=2657860
IDBENCH=1437
IDSOLVER=1163
FILE ID=node026/2657860-1276328886
PBS_JOBID= 11173158
Free space on /tmp= 62508 MiB

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

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

MD5SUM BENCH= 05acc78c42ec3368f84785abcf0f7ebb
RANDOM SEED=909727446

node026.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.201
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.40
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.201
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.46
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1851920 kB
Buffers:         14176 kB
Cached:         103628 kB
SwapCached:      23112 kB
Active:         101924 kB
Inactive:        41320 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1851920 kB
SwapTotal:     4192956 kB
SwapFree:      4135896 kB
Dirty:            4452 kB
Writeback:           0 kB
AnonPages:       10200 kB
Mapped:           8096 kB
Slab:            42196 kB
PageTables:       3984 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180364 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= 62508 MiB
End job on node026 at 2010-06-12 09:48:06