Trace number 2669086

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
PB/CT 0.1SAT 0.080986 0.0814001

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga14_13_sat_pb.cnf.cr.opb
MD5SUMc93baf194c905dcd2c2597569ae179ef
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.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 variables273
Total number of constraints222
Number of constraints which are clauses195
Number of constraints which are cardinality constraints (but not clauses)27
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint7
Maximum length of a constraint14
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 15
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 PB/CT 0.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.00	c constraints 27/0 clauses 195/0 units 0
0.00/0.00	c vars 273
0.02/0.07	c 0.06099 5.53516 496 1217
0.02/0.07	s SATISFIABLE
0.02/0.07	v -x1 -x2 -x3 -x4 -x5 -x6 -x7 -x8 -x9 -x10 -x11 -x12 -x13 x14 -x15 -x16 -x17 -x18 -x19 -x20 x21 -x22 -x23 -x24 -x25 -x26 -x27 -x28 -x29 -x30 -x31 -x32 x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 x48 -x49 -x50 -x51 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 x65 -x66 -x67 -x68 -x69 -x70 -x71 x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80 -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105 -x106 -x107 -x108 -x109 -x110 x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 x122 -x123 -x124 -x125 -x126 x127 -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 -x136 -x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147 x148 -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 x166 -x167 -x168 -x169 -x170 x171 -x172 -x173 -x174 -x175 -x176 -x177 -x178 -x179 -x180 -x181 -x182 x183 -x184 -x185 -x186 -x187 -x188 -x189 -x190 -x191 -x192 -x193 x194 -x195 -x196 -x197 -x198 x199 -x200 -x201 -x202 -x203 -x204 -x205 -x206 -x207 -x208 x209 -x210 -x211 -x212 -x213 x214 -x215 -x216 -x217 -x218 -x219 -x220 -x221 x222 -x223 -x224 -x225 -x226 -x227 -x228 x229 -x230 -x231 -x232 -x233 -x234 -x235 -x236 -x237 x238 -x239 -x240 -x241 -x242 -x243 x244 -x245 -x246 -x247 -x248 x249 -x250 -x251 -x252 -x253 x254 -x255 -x256 -x257 -x258 -x259 x260 -x261 -x262 -x263 -x264 -x265 -x266 -x267 -x268 x269 -x270 -x271 -x272 -x273

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-2669086-1276435172/watcher-2669086-1276435172 -o /tmp/evaluation-result-2669086-1276435172/solver-2669086-1276435172 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2669086-1276435172.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.04 1.01 1.00 3/106 22048
/proc/meminfo: memFree=1798348/2059040 swapFree=4140364/4192956
[pid=22048] ppid=22046 vsize=3120 CPUtime=0
/proc/22048/stat : 22048 (pbct) R 22046 22048 21373 0 -1 4202496 459 0 0 0 0 0 0 0 24 0 1 0 17169089 3194880 382 1992294400 134512640 136485738 4293780448 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/22048/statm: 780 383 191 482 0 296 0

[startup+0.0297531 s]
/proc/loadavg: 1.04 1.01 1.00 3/106 22048
/proc/meminfo: memFree=1798348/2059040 swapFree=4140364/4192956
[pid=22048] ppid=22046 vsize=5404 CPUtime=0.02
/proc/22048/stat : 22048 (pbct) R 22046 22048 21373 0 -1 4202496 1036 0 0 0 2 0 0 0 24 0 1 0 17169089 5533696 959 1992294400 134512640 136485738 4293780448 18446744073709551615 134933016 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/22048/statm: 1351 959 208 482 0 867 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5404

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

[startup+0.0297531 s]
/proc/loadavg: 1.04 1.01 1.00 3/106 22048
/proc/meminfo: memFree=1798348/2059040 swapFree=4140364/4192956
[pid=22048] ppid=22046 vsize=5404 CPUtime=0.02
/proc/22048/stat : 22048 (pbct) R 22046 22048 21373 0 -1 4202496 1036 0 0 0 2 0 0 0 24 0 1 0 17169089 5533696 959 1992294400 134512640 136485738 4293780448 18446744073709551615 134933016 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/22048/statm: 1351 959 208 482 0 867 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 5404

Child status: 0
Real time (s): 0.0814001
CPU time (s): 0.080986
CPU user time (s): 0.066989
CPU system time (s): 0.013997
CPU usage (%): 99.4913
Max. virtual memory (cumulated for all children) (KiB): 5404

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.066989
system time used= 0.013997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1135
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.006998 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node027 at 2010-06-13 15:19:32
IDJOB=2669086
IDBENCH=1432
IDSOLVER=1170
FILE ID=node027/2669086-1276435172
PBS_JOBID= 11173310
Free space on /tmp= 62448 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-fpga14_13_sat_pb.cnf.cr.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2669086-1276435172/watcher-2669086-1276435172 -o /tmp/evaluation-result-2669086-1276435172/solver-2669086-1276435172 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2669086-1276435172.opb

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

MD5SUM BENCH= c93baf194c905dcd2c2597569ae179ef
RANDOM SEED=1960006469

node027.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		: 2800.261
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	: 5600.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		: 2800.261
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:       1798876 kB
Buffers:         52312 kB
Cached:         127788 kB
SwapCached:       6492 kB
Active:          94016 kB
Inactive:        99504 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1798876 kB
SwapTotal:     4192956 kB
SwapFree:      4140364 kB
Dirty:            2032 kB
Writeback:           0 kB
AnonPages:       11108 kB
Mapped:          12932 kB
Slab:            44840 kB
PageTables:       3984 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181476 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264952 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62444 MiB
End job on node027 at 2010-06-13 15:19:33