Trace number 361365

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.16SAT 0.021996 0.0360039

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga12_11_sat_pb.cnf.cr.opb
MD5SUM05acc78c42ec3368f84785abcf0f7ebb
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.002999
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 (download as text)

0.00/0.00	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 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 Time Limit set to 1800
0.00/0.00	c Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/361365-1176982406/instance-361365-1176982406.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.01	c Total parsing time: 0.001 s
0.00/0.01	c Var: 198 Constr: 166 143/23/0 Lit: 1188 Watch. Lit: 484
0.00/0.01	c Obj. Vars: 0 (0 % of total variables)
0.00/0.02	c Pre-processing Time: 0.004 s
0.00/0.02	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.02	c        0    198      166     1188    7      484     597      0      0 0.00
0.00/0.02	c Switching off LPR mode.
0.00/0.03	c      101    198      267     3814   14      686     657    101  14428 0.01
0.00/0.03	c      251    198      417    10529   25      986     723    251  16733 0.01
0.00/0.03	v x76 -x148 -x149 x150 -x151 -x152 x32 -x169 -x170 -x171 -x172 -x173 x174 -x85 x133 -x134 -x135 -x136 -x137 -x73 -x109 -x16 -x100
0.00/0.03	v x123 -x143 x144 -x145 -x146 -x147 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 x120 -x98 -x138 -x139 -x140
0.00/0.03	v -x141 x142 -x61 -x57 -x175 -x176 x177 -x178 -x179 -x180 -x41 -x153 -x154 -x155 x156 -x157 -x63 x9 -x187 x188 -x189 -x190 -x191
0.00/0.03	v -x192 -x8 -x26 -x45 -x37 -x68 -x72 -x193 -x194 -x195 -x196 x197 -x198 -x33 -x65 -x129 -x86 -x87 -x88 x89 -x90 -x91 -x92 -x93
0.00/0.03	v -x94 -x95 -x96 -x75 x97 -x99 -x101 -x102 -x103 -x104 -x105 -x106 -x107 -x108 -x62 -x64 -x66 -x67 -x69 -x70 x71 -x79 x163 -x164
0.00/0.03	v -x165 -x166 -x167 -x168 -x14 -x20 -x125 x50 -x40 -x42 -x158 -x159 -x160 -x161 -x162 -x60 x19 -x49 -x51 -x52 -x53 -x54 -x55 -x56
0.00/0.03	v -x58 -x59 -x1 -x12 -x21 -x35 -x78 -x13 -x121 -x122 -x124 -x126 -x127 -x128 -x130 -x131 -x132 -x80 -x181 -x182 -x183 x184 -x185
0.00/0.03	v -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
0.00/0.03	v x46 -x48 -x81 -x82 -x83 -x10 -x2 -x5 -x22 -x24
0.00/0.03	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.03	c    2      258     74      934      424    10867    258  16125 0.02
0.00/0.03	s SATISFIABLE
0.00/0.03	c Total time: 0.016 s

Verifier Data (download as text)

OK	0

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node42/watcher-361365-1176982406 -o ROOT/results/node42/solver-361365-1176982406 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361365-1176982406/instance-361365-1176982406.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: 1.09 1.00 0.96 3/77 6621
/proc/meminfo: memFree=1584448/2055920 swapFree=4129056/4192956
[pid=6621] ppid=6619 vsize=11748 CPUtime=0
/proc/6621/stat : 6621 (bsolo3.0.16) R 6619 6621 5380 0 -1 4194304 369 0 0 0 0 0 0 0 18 0 1 0 146152512 12029952 337 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 12842619 0 0 4096 16384 0 0 0 17 1 0 0
/proc/6621/statm: 2937 337 283 324 0 2003 0

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

Child status: 0
Real time (s): 0.0360039
CPU time (s): 0.021996
CPU user time (s): 0.016997
CPU system time (s): 0.004999
CPU usage (%): 61.0933
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.016997
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= 453
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 13
involuntary context switches= 10

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node42 on Thu Apr 19 11:33:26 UTC 2007

IDJOB= 361365
IDBENCH= 1437
IDSOLVER= 163
FILE ID= node42/361365-1176982406

PBS_JOBID= 4630364

Free space on /tmp= 66445 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-fpga12_11_sat_pb.cnf.cr.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361365-1176982406/instance-361365-1176982406.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node42/watcher-361365-1176982406 -o ROOT/results/node42/solver-361365-1176982406 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361365-1176982406/instance-361365-1176982406.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  05acc78c42ec3368f84785abcf0f7ebb

RANDOM SEED= 37144608

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node42.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.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:       1584920 kB
Buffers:         34568 kB
Cached:         347384 kB
SwapCached:      17616 kB
Active:          82284 kB
Inactive:       331452 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1584920 kB
SwapTotal:     4192956 kB
SwapFree:      4129056 kB
Dirty:            4600 kB
Writeback:           0 kB
Mapped:          39552 kB
Slab:            42700 kB
Committed_AS:  2995044 kB
PageTables:       1912 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= 66445 MiB

End job on node42 on Thu Apr 19 11:33:26 UTC 2007