Trace number 1880517

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 NameAnswerobjCPU timeWall clock time
bsolo 3.1 pbUNSAT 0.208967 0.209556

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-bf1355-075.opb
MD5SUMf91b1a8ba871517e9c6c65d2a92ea818
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkUNSAT
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark0.145977
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables4360
Total number of constraints8958
Number of constraints which are clauses8958
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint6
Number of terms in the objective function 4360
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 4360
Number of bits of the sum of numbers in the objective function 13
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 4360
Number of bits of the biggest sum of numbers13
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.1 - 13/04/2009 : 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 Learning Strategy: Generic Pseudo-Boolean Learning
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 HOME/instance-1880517-1245158530.opb
0.00/0.00	c File size is 290693 bytes.
0.01/0.04	c Highest Coefficient sum: 4360
0.01/0.04	c Parsing was ok!!
0.01/0.04	c Total parsing time: 0.041 s
0.01/0.04	c Var: 4360 Constr: 8958 8958/0/0 Lit: 21470 Watch. Lit: 17911
0.01/0.04	c Obj. Vars: 4360 (100 % of total variables)
0.19/0.20	c Pre-processing Time: 0.204 s
0.19/0.20	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.19/0.20	c        0    954     2865     7456    2     5730     954      0      0 0.20
0.19/0.20	c Switching off lower bounding mode.
0.19/0.20	c Backtracks by Clause: 14
0.19/0.20	c Backtracks by PB constraint: 1
0.19/0.20	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.19/0.20	c    0       15      6       80     2892     7536     27     72 0.21
0.19/0.20	s UNSATISFIABLE
0.19/0.20	c Total time: 0.206 s

Verifier Data 

ERROR: no interpretation found !

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1880517-1245158530/watcher-1880517-1245158530 -o /tmp/evaluation-result-1880517-1245158530/solver-1880517-1245158530 -C 1800 -W 2000 -M 1800 bsolo -l3 -t1800 -m1800 HOME/instance-1880517-1245158530.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: 0.78 0.94 0.98 3/64 4660
/proc/meminfo: memFree=1919592/2055920 swapFree=4191900/4192956
[pid=4660] ppid=4658 vsize=18812 CPUtime=0
/proc/4660/stat : 4660 (bsolo) R 4658 4660 4617 0 -1 4194304 261 0 0 0 0 0 0 0 18 0 1 0 183453952 19263488 245 1992294400 134512640 137136520 4294956256 18446744073709551615 136504651 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4660/statm: 4703 245 172 640 0 3988 0

[startup+0.018686 s]
/proc/loadavg: 0.78 0.94 0.98 3/64 4660
/proc/meminfo: memFree=1919592/2055920 swapFree=4191900/4192956
[pid=4660] ppid=4658 vsize=11472 CPUtime=0.01
/proc/4660/stat : 4660 (bsolo) R 4658 4660 4617 0 -1 4194304 406 0 0 0 1 0 0 0 18 0 1 0 183453952 11747328 390 1992294400 134512640 137136520 4294956256 18446744073709551615 136504651 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4660/statm: 2868 390 197 640 0 2153 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 11472

[startup+0.101694 s]
/proc/loadavg: 0.78 0.94 0.98 3/64 4660
/proc/meminfo: memFree=1919592/2055920 swapFree=4191900/4192956
[pid=4660] ppid=4658 vsize=12672 CPUtime=0.09
/proc/4660/stat : 4660 (bsolo) R 4658 4660 4617 0 -1 4194304 819 0 0 0 9 0 0 0 18 0 1 0 183453952 12976128 732 1992294400 134512640 137136520 4294956256 18446744073709551615 136568305 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4660/statm: 3168 732 188 640 0 2524 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 12672

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

[startup+0.201702 s]
/proc/loadavg: 0.78 0.94 0.98 3/64 4660
/proc/meminfo: memFree=1919592/2055920 swapFree=4191900/4192956
[pid=4660] ppid=4658 vsize=12724 CPUtime=0.19
/proc/4660/stat : 4660 (bsolo) R 4658 4660 4617 0 -1 4194304 856 0 0 0 18 1 0 0 18 0 1 0 183453952 13029376 767 1992294400 134512640 137136520 4294956256 18446744073709551615 136568305 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4660/statm: 3181 767 192 640 0 2537 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 12724

Child status: 0
Real time (s): 0.209556
CPU time (s): 0.208967
CPU user time (s): 0.19497
CPU system time (s): 0.013997
CPU usage (%): 99.7189
Max. virtual memory (cumulated for all children) (KiB): 12724

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.19497
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= 862
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= 2
involuntary context switches= 0

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node14 at 2009-06-16 15:22:10
IDJOB=1880517
IDBENCH=2169
IDSOLVER=701
FILE ID=node14/1880517-1245158530
PBS_JOBID= 9363845
Free space on /tmp= 66376 MiB

SOLVER NAME= bsolo 3.1 pb
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-bf1355-075.opb
COMMAND LINE= bsolo -l3 -tTIMEOUT -mMEMLIMIT BENCHNAME
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1880517-1245158530/watcher-1880517-1245158530 -o /tmp/evaluation-result-1880517-1245158530/solver-1880517-1245158530 -C 1800 -W 2000 -M 1800  bsolo -l3 -t1800 -m1800 HOME/instance-1880517-1245158530.opb

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

MD5SUM BENCH= f91b1a8ba871517e9c6c65d2a92ea818
RANDOM SEED=2049765453

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

/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.234
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.234
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:       1919944 kB
Buffers:         24340 kB
Cached:          56668 kB
SwapCached:        388 kB
Active:          46244 kB
Inactive:        48076 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1919944 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            4584 kB
Writeback:           0 kB
Mapped:          21656 kB
Slab:            27584 kB
Committed_AS:   176136 kB
PageTables:       1452 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-1880517-1245158530.opb

Free space on /tmp at the end= 66372 MiB
End job on node14 at 2009-06-16 15:22:11