Trace number 1880190

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.1 pbUNSAT 3.10253 3.10384

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1111218757.opb
MD5SUMd6496b44145c310b75c0b7261c5aa1e2
Bench CategoryDEC-SMALLINT (no 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.194969
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables169
Total number of constraints101
Number of constraints which are clauses30
Number of constraints which are cardinality constraints (but not clauses)70
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint169
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 38
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 1266
Number of bits of the biggest sum of numbers11
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-1880190-1245115913.opb
0.00/0.00	c File size is 9903 bytes.
0.00/0.00	c Highest Coefficient sum: 1266
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: 169 Constr: 101 30/70/1 Lit: 1205 Watch. Lit: 903
0.00/0.00	c Obj. Vars: 0 (0 % of total variables)
0.00/0.00	c Pre-processing Time: 0.005 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0    169       99     1179   11      883    2563      0      0 0.01
0.00/0.00	c Switching off lower bounding mode.
3.09/3.10	c      100    169      298    18896   63    11661    2820    199   1818 0.06
3.09/3.10	c      252    169      601    47129   78    27744    3103    502   1155 0.22
3.09/3.10	c      478    169     1050    88591   84    49138    3414    951    858 0.56
3.09/3.10	c      816    169     1720   153344   89    77535    3756   1621    612 1.33
3.09/3.10	c     1326     92     2684   237760   88   112109    4132   2585    450 2.95
3.09/3.10	c Backtracks by Clause: 1153
3.09/3.10	c Backtracks by PB constraint: 155
3.09/3.10	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
3.09/3.10	c    5     1370    226     1924     2769   243838   2670    442 3.10
3.09/3.10	s UNSATISFIABLE
3.09/3.10	c Total time: 3.099 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-1880190-1245115913/watcher-1880190-1245115913 -o /tmp/evaluation-result-1880190-1245115913/solver-1880190-1245115913 -C 1800 -W 2000 -M 1800 bsolo -l3 -t1800 -m1800 HOME/instance-1880190-1245115913.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.13 1.03 1.08 2/64 1829
/proc/meminfo: memFree=1407280/2055920 swapFree=4191900/4192956
[pid=1829] ppid=1827 vsize=10708 CPUtime=0
/proc/1829/stat : 1829 (bsolo) R 1827 1829 1150 0 -1 4194304 258 0 0 0 0 0 0 0 18 0 1 0 179187979 10964992 239 1992294400 134512640 137136520 4294956256 18446744073709551615 136568305 0 0 4096 16384 0 0 0 17 1 0 0
/proc/1829/statm: 2677 239 188 640 0 2033 0

[startup+0.099872 s]
/proc/loadavg: 1.13 1.03 1.08 2/64 1829
/proc/meminfo: memFree=1407280/2055920 swapFree=4191900/4192956
[pid=1829] ppid=1827 vsize=11356 CPUtime=0.09
/proc/1829/stat : 1829 (bsolo) R 1827 1829 1150 0 -1 4194304 455 0 0 0 9 0 0 0 18 0 1 0 179187979 11628544 436 1992294400 134512640 137136520 4294956256 18446744073709551615 136504651 0 0 4096 16384 0 0 0 17 1 0 0
/proc/1829/statm: 2839 436 197 640 0 2195 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11356

[startup+0.102872 s]
/proc/loadavg: 1.13 1.03 1.08 2/64 1829
/proc/meminfo: memFree=1407280/2055920 swapFree=4191900/4192956
[pid=1829] ppid=1827 vsize=11484 CPUtime=0.09
/proc/1829/stat : 1829 (bsolo) R 1827 1829 1150 0 -1 4194304 458 0 0 0 9 0 0 0 18 0 1 0 179187979 11759616 439 1992294400 134512640 137136520 4294956256 18446744073709551615 136698750 0 0 4096 16384 0 0 0 17 1 0 0
/proc/1829/statm: 2871 439 197 640 0 2227 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11484

[startup+0.302908 s]
/proc/loadavg: 1.13 1.03 1.08 2/64 1829
/proc/meminfo: memFree=1407280/2055920 swapFree=4191900/4192956
[pid=1829] ppid=1827 vsize=12256 CPUtime=0.29
/proc/1829/stat : 1829 (bsolo) R 1827 1829 1150 0 -1 4194304 656 0 0 0 29 0 0 0 19 0 1 0 179187979 12550144 637 1992294400 134512640 137136520 4294956256 18446744073709551615 134544256 0 0 4096 16384 0 0 0 17 1 0 0
/proc/1829/statm: 3064 637 197 640 0 2420 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 12256

[startup+0.701982 s]
/proc/loadavg: 1.13 1.03 1.08 2/64 1829
/proc/meminfo: memFree=1407280/2055920 swapFree=4191900/4192956
[pid=1829] ppid=1827 vsize=13428 CPUtime=0.69
/proc/1829/stat : 1829 (bsolo) R 1827 1829 1150 0 -1 4194304 947 0 0 0 69 0 0 0 22 0 1 0 179187979 13750272 928 1992294400 134512640 137136520 4294956256 18446744073709551615 134544160 0 0 4096 16384 0 0 0 17 1 0 0
/proc/1829/statm: 3357 928 197 640 0 2713 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 13428

[startup+1.50113 s]
/proc/loadavg: 1.13 1.03 1.08 2/65 1830
/proc/meminfo: memFree=1403688/2055920 swapFree=4191900/4192956
[pid=1829] ppid=1827 vsize=14732 CPUtime=1.49
/proc/1829/stat : 1829 (bsolo) R 1827 1829 1150 0 -1 4194304 1286 0 0 0 149 0 0 0 25 0 1 0 179187979 15085568 1267 1992294400 134512640 137136520 4294956256 18446744073709551615 136509112 0 0 4096 16384 0 0 0 17 1 0 0
/proc/1829/statm: 3683 1267 197 640 0 3039 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 14732

[startup+3.10142 s]
/proc/loadavg: 1.13 1.03 1.08 2/65 1830
/proc/meminfo: memFree=1401960/2055920 swapFree=4191900/4192956
[pid=1829] ppid=1827 vsize=16688 CPUtime=3.09
/proc/1829/stat : 1829 (bsolo) R 1827 1829 1150 0 -1 4194304 1762 0 0 0 308 1 0 0 25 0 1 0 179187979 17088512 1743 1992294400 134512640 137136520 4294956256 18446744073709551615 134544116 0 0 4096 16384 0 0 0 17 1 0 0
/proc/1829/statm: 4172 1743 197 640 0 3528 0
Current children cumulated CPU time (s) 3.09
Current children cumulated vsize (KiB) 16688

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

Child status: 0
Real time (s): 3.10384
CPU time (s): 3.10253
CPU user time (s): 3.08753
CPU system time (s): 0.014997
CPU usage (%): 99.9579
Max. virtual memory (cumulated for all children) (KiB): 16688

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 3.08753
system time used= 0.014997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1764
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= 7

runsolver used 0.007998 second user time and 0.011998 second system time

The end

Launcher Data 

Begin job on node44 at 2009-06-16 03:31:53
IDJOB=1880190
IDBENCH=1259
IDSOLVER=701
FILE ID=node44/1880190-1245115913
PBS_JOBID= 9363664
Free space on /tmp= 65924 MiB

SOLVER NAME= bsolo 3.1 pb
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/wnqueen/normalized-t2001.13queen13.1111218757.opb
COMMAND LINE= bsolo -l3 -tTIMEOUT -mMEMLIMIT BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1880190-1245115913/watcher-1880190-1245115913 -o /tmp/evaluation-result-1880190-1245115913/solver-1880190-1245115913 -C 1800 -W 2000 -M 1800  bsolo -l3 -t1800 -m1800 HOME/instance-1880190-1245115913.opb

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

MD5SUM BENCH= d6496b44145c310b75c0b7261c5aa1e2
RANDOM SEED=59155879

node44.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.263
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.263
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:       1407696 kB
Buffers:         39912 kB
Cached:         526404 kB
SwapCached:        260 kB
Active:          58788 kB
Inactive:       520816 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1407696 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            4384 kB
Writeback:           0 kB
Mapped:          21748 kB
Slab:            54572 kB
Committed_AS:   156612 kB
PageTables:       1384 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= 65920 MiB
End job on node44 at 2009-06-16 03:31:56