Trace number 2657965

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 NameAnswerobjective functionCPU timeWall clock time
bsolo 3.2 ClUNSAT 0.274957 0.273965

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-ssa6288-047.opb
MD5SUM74304bad8e53580b77abf30e0c0ba7f6
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.272958
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables20820
Total number of constraints44648
Number of constraints which are clauses44648
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 20820
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 20820
Number of bits of the sum of numbers in the objective function 15
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 20820
Number of bits of the biggest sum of numbers15
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.2 - 23/05/2010 : 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 Time Limit set to 1800
0.00/0.00	c Learning Strategy: Clause Learning
0.00/0.00	c Instance file HOME/instance-2657965-1276420301.opb
0.00/0.00	c File size is 1543946 bytes.
0.19/0.25	c Highest Coefficient sum: 20820
0.19/0.25	c Parsing was ok!!
0.19/0.25	c Total parsing time: 0.25 s
0.19/0.27	c Var: 20820 Constr: 44648 44648/0/0 Lit: 108243 Watch. Lit: 89292
0.19/0.27	c Obj. Vars: 20820 (100 % of total variables)
0.19/0.27	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.19/0.27	c    0        0      0        0    44648   108243      0      0 0.27
0.19/0.27	s UNSATISFIABLE
0.19/0.27	c Total time: 0.271 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-2657965-1276420301/watcher-2657965-1276420301 -o /tmp/evaluation-result-2657965-1276420301/solver-2657965-1276420301 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l1 HOME/instance-2657965-1276420301.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.92 1.10 1.45 3/106 24644
/proc/meminfo: memFree=1852048/2059040 swapFree=4135604/4192956
[pid=24644] ppid=24642 vsize=20268 CPUtime=0
/proc/24644/stat : 24644 (bsolo_pb10) R 24642 24644 24429 0 -1 4202496 361 0 0 0 0 0 0 0 18 0 1 0 17634093 20754432 279 1992294400 134512640 137138936 4292979856 18446744073709551615 136577166 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/24644/statm: 5067 280 172 642 0 4046 0

[startup+0.0531381 s]
/proc/loadavg: 0.92 1.10 1.45 3/106 24644
/proc/meminfo: memFree=1852048/2059040 swapFree=4135604/4192956
[pid=24644] ppid=24642 vsize=14376 CPUtime=0.04
/proc/24644/stat : 24644 (bsolo_pb10) R 24642 24644 24429 0 -1 4202496 928 0 0 0 4 0 0 0 20 0 1 0 17634093 14721024 806 1992294400 134512640 137138936 4292979856 18446744073709551615 136525315 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/24644/statm: 3594 807 239 642 0 2573 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 14376

[startup+0.101142 s]
/proc/loadavg: 0.92 1.10 1.45 3/106 24644
/proc/meminfo: memFree=1852048/2059040 swapFree=4135604/4192956
[pid=24644] ppid=24642 vsize=15476 CPUtime=0.09
/proc/24644/stat : 24644 (bsolo_pb10) R 24642 24644 24429 0 -1 4202496 1277 0 0 0 9 0 0 0 20 0 1 0 17634093 15847424 1155 1992294400 134512640 137138936 4292979856 18446744073709551615 134531572 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/24644/statm: 3869 1155 310 642 0 2848 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 15476

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

[startup+0.201154 s]
/proc/loadavg: 0.92 1.10 1.45 3/106 24644
/proc/meminfo: memFree=1852048/2059040 swapFree=4135604/4192956
[pid=24644] ppid=24642 vsize=17392 CPUtime=0.19
/proc/24644/stat : 24644 (bsolo_pb10) R 24642 24644 24429 0 -1 4202496 1921 0 0 0 19 0 0 0 20 0 1 0 17634093 17809408 1799 1992294400 134512640 137138936 4292979856 18446744073709551615 134531606 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/24644/statm: 4348 1799 461 642 0 3327 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 17392

Child status: 0
Real time (s): 0.273965
CPU time (s): 0.274957
CPU user time (s): 0.25996
CPU system time (s): 0.014997
CPU usage (%): 100.362
Max. virtual memory (cumulated for all children) (KiB): 17392

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.25996
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= 3211
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= 6

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node002 at 2010-06-13 11:11:41
IDJOB=2657965
IDBENCH=2068
IDSOLVER=1163
FILE ID=node002/2657965-1276420301
PBS_JOBID= 11173299
Free space on /tmp= 62396 MiB

SOLVER NAME= bsolo 3.2 Cl
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-ssa6288-047.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l1 BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2657965-1276420301/watcher-2657965-1276420301 -o /tmp/evaluation-result-2657965-1276420301/solver-2657965-1276420301 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l1 HOME/instance-2657965-1276420301.opb

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

MD5SUM BENCH= 74304bad8e53580b77abf30e0c0ba7f6
RANDOM SEED=31105044

node002.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		: 3000.242
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	: 6000.48
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.242
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.36
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1852576 kB
Buffers:          9976 kB
Cached:         120012 kB
SwapCached:      10340 kB
Active:          27460 kB
Inactive:       115060 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1852576 kB
SwapTotal:     4192956 kB
SwapFree:      4135604 kB
Dirty:            5464 kB
Writeback:           4 kB
AnonPages:       11036 kB
Mapped:           9220 kB
Slab:            42284 kB
PageTables:       4060 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181052 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62392 MiB
End job on node002 at 2010-06-13 11:11:42