Trace number 432412

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 3.0.17SAT 0.014997 0.0177839

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga13_12_sat_pb.cnf.cr.opb
MD5SUM774e61576b805c95b87ab57992a33004
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.003999
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables234
Total number of constraints193
Number of constraints which are clauses168
Number of constraints which are cardinality constraints (but not clauses)25
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/0.00	c bsolo beta version 3.0.17 - 27/04/2007 : 1600 GMT
0.00/0.00	c Developed by Vasco Manquinho 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 Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/432412-1177943623/instance-432412-1177943623.opb
0.00/0.00	c File size is 13109 bytes.
0.00/0.00	c Highest Coefficient sum: 14
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0.003 s
0.00/0.00	c Var: 234 Constr: 193 168/25/0 Lit: 1482 Watch. Lit: 570
0.00/0.00	c Obj. Vars: 0 (0 % of total variables)
0.00/0.01	c Pre-processing Time: 0.006 s
0.00/0.01	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.01	c        0    234      193     1482    7      570     771      0      0 0.01
0.00/0.01	c Switching off LPR mode.
0.00/0.01	c      100    234      293     8124   27      770     849    100   8333 0.01
0.00/0.01	v -x67 -x163 -x164 x165 -x166 -x167 -x168 -x18 -x181 -x182 -x183 -x184 x185 -x186 -x53 -x157 -x158 -x159 x160 -x161 -x162 -x139
0.00/0.01	v -x205 -x206 x207 -x208 -x209 -x210 -x137 -x193 x194 -x195 -x196 -x197 -x198 -x46 x119 -x130 -x229 -x230 -x231 -x232 x233 -x234
0.00/0.01	v x141 -x217 -x218 -x219 x220 -x221 -x222 -x14 -x15 -x16 -x17 -x19 x20 -x21 -x22 -x23 -x24 -x25 -x26 -x37 x31 -x7 -x63 -x74 -x93
0.00/0.01	v -x128 -x134 -x175 -x176 -x177 -x178 -x179 x180 -x77 -x223 -x224 -x225 -x226 -x227 x228 x79 x97 -x187 x188 -x189 -x190 -x191
0.00/0.01	v -x192 -x110 -x44 -x48 -x52 x64 -x87 -x117 -x71 x113 -x66 -x58 x4 -x33 -x103 x156 x49 x211 -x212 -x213 -x214 -x215 -x216 -x11
0.00/0.01	v -x140 -x35 x68 -x69 -x70 -x72 -x73 -x75 -x76 -x78 -x3 x169 -x170 -x171 -x172 -x173 -x174 -x132 -x32 -x152 -x99 -x199 -x200 -x201
0.00/0.01	v -x202 -x203 -x204 -x57 -x27 -x28 -x29 -x30 -x34 -x36 -x38 -x39 -x55 -x125 -x84 -x131 -x133 -x135 -x136 -x138 -x142 -x143 -x109
0.00/0.01	v -x50 -x65 -x80 -x150 -x105 -x106 -x107 -x108 -x111 -x112 -x114 -x115 -x116 -x51 -x129 -x121 -x145 -x41 -x10 -x86 -x12 -x81
0.00/0.01	v -x82 -x83 -x85 -x88 -x89 -x90 -x91 -x40 -x42 -x43 -x45 -x47 -x154 -x148 -x92 -x126 -x60 -x54 -x56 -x59 -x61 -x62 -x124 -x118
0.00/0.01	v -x120 -x122 -x123 -x127 -x96 -x102 -x1 -x151 -x155 -x95 -x94 -x98 -x100 -x101 -x104 -x153 -x6 -x13 -x5 -x144 -x2 -x146 -x147
0.00/0.01	v -x149 -x8 -x9
0.00/0.01	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.01	c    1      100     27      430      293     8124    100   8333 0.01
0.00/0.01	s SATISFIABLE
0.00/0.01	c Total time: 0.012 s

Verifier Data (download as text)

OK	0

Watcher Data (download as text)

runsolver version 3.2.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node47/watcher-432412-1177943623 -o ROOT/results/node47/solver-432412-1177943623 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.17 -m1800 /tmp/evaluation/432412-1177943623/instance-432412-1177943623.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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.91 0.95 0.85 3/77 26772
/proc/meminfo: memFree=1627576/2055920 swapFree=4158036/4192956
[pid=26772] ppid=26770 vsize=11752 CPUtime=0
/proc/26772/stat : 26772 (bsolo3.0.17) R 26770 26772 26220 0 -1 4194304 365 0 0 0 0 0 0 0 18 0 1 0 149207664 12034048 335 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 134536769 0 0 4096 16384 0 0 0 17 1 0 0
/proc/26772/statm: 2938 335 281 324 0 2004 0

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

Child status: 0
Real time (s): 0.0177839
CPU time (s): 0.014997
CPU user time (s): 0.011998
CPU system time (s): 0.002999
CPU usage (%): 84.3292
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.011998
system time used= 0.002999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 443
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= 12
involuntary context switches= 0

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node47 on Mon Apr 30 14:33:43 UTC 2007

IDJOB= 432412
IDBENCH= 1399
IDSOLVER= 199
FILE ID= node47/432412-1177943623

PBS_JOBID= 4727548

Free space on /tmp= 66558 MiB

SOLVER NAME= bsolo 3.0.17
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-fpga13_12_sat_pb.cnf.cr.opb
COMMAND LINE= bsolo3.0.17 -m1800 /tmp/evaluation/432412-1177943623/instance-432412-1177943623.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node47/watcher-432412-1177943623 -o ROOT/results/node47/solver-432412-1177943623 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.17 -m1800 /tmp/evaluation/432412-1177943623/instance-432412-1177943623.opb            

META MD5SUM SOLVER= c9b15312c639dd71a11a1e3ca1b27020
MD5SUM BENCH=  774e61576b805c95b87ab57992a33004

RANDOM SEED= 657787209

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node47.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.221
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.221
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:       1627984 kB
Buffers:         41172 kB
Cached:         292344 kB
SwapCached:       3492 kB
Active:         228764 kB
Inactive:       128668 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1627984 kB
SwapTotal:     4192956 kB
SwapFree:      4158036 kB
Dirty:            6704 kB
Writeback:           0 kB
Mapped:          30968 kB
Slab:            56012 kB
Committed_AS:  4044876 kB
PageTables:       1780 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66558 MiB

End job on node47 on Mon Apr 30 14:33:43 UTC 2007