Trace number 433015

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 NameAnswerObjective functionCPU timeWall clock time
bsolo 3.0.17UNSAT 0.089985 0.0906531

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-ssa2670-141.opb
MD5SUMbf686e12342472d00013af54a5ee9279
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.089985
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables1972
Total number of constraints3301
Number of constraints which are clauses3301
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 constraint5
Number of terms in the objective function 1972
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 1972
Number of bits of the sum of numbers in the objective function 11
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 1972
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 (download as text)

0.00/0.00	c bsolo beta version 3.0.17 - 27/04/2007 : 1600 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 Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/433015-1177952921/instance-433015-1177952921.opb
0.00/0.00	c File size is 101262 bytes.
0.00/0.03	c Highest Coefficient sum: 1972
0.00/0.03	c Parsing was ok!!
0.00/0.03	c Total parsing time: 0.034 s
0.00/0.03	c Var: 1972 Constr: 3301 3301/0/0 Lit: 7210 Watch. Lit: 6598
0.00/0.03	c Obj. Vars: 1972 (100 % of total variables)
0.05/0.07	c Pre-processing Time: 0.073 s
0.05/0.07	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.05/0.07	c        0    373      922     2348    2     1844     307      0      0 0.07
0.05/0.07	c Switching off LPR mode.
0.05/0.08	c      101    373     1023     3715    3     2046     338    101   1294 0.08
0.05/0.08	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.05/0.08	c    1      240     85      555     1162     5278    240   2823 0.09
0.05/0.08	s UNSATISFIABLE
0.05/0.08	c Total time: 0.085 s

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node39/watcher-433015-1177952921 -o ROOT/results/node39/solver-433015-1177952921 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.17 -m1800 /tmp/evaluation/433015-1177952921/instance-433015-1177952921.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: 0.92 1.00 0.96 3/77 16149
/proc/meminfo: memFree=1711024/2055920 swapFree=4159396/4192956
[pid=16149] ppid=16147 vsize=11836 CPUtime=0
/proc/16149/stat : 16149 (bsolo3.0.17) R 16147 16149 14609 0 -1 4194304 363 0 0 0 0 0 0 0 18 0 1 0 243204187 12120064 333 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/16149/statm: 2959 333 279 324 0 2004 0

[startup+0.0633951 s]
/proc/loadavg: 0.92 1.00 0.96 3/77 16149
/proc/meminfo: memFree=1711024/2055920 swapFree=4159396/4192956
[pid=16149] ppid=16147 vsize=4772 CPUtime=0.05
/proc/16149/stat : 16149 (bsolo3.0.17) R 16147 16149 14609 0 -1 4194304 602 0 0 0 5 0 0 0 18 0 1 0 243204187 4886528 547 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/16149/statm: 1193 547 302 324 0 263 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 4772

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

[startup+0.0633951 s]
/proc/loadavg: 0.92 1.00 0.96 3/77 16149
/proc/meminfo: memFree=1711024/2055920 swapFree=4159396/4192956
[pid=16149] ppid=16147 vsize=4772 CPUtime=0.05
/proc/16149/stat : 16149 (bsolo3.0.17) R 16147 16149 14609 0 -1 4194304 602 0 0 0 5 0 0 0 18 0 1 0 243204187 4886528 547 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/16149/statm: 1193 547 302 324 0 263 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 4772

Child status: 0
Real time (s): 0.0906531
CPU time (s): 0.089985
CPU user time (s): 0.080987
CPU system time (s): 0.008998
CPU usage (%): 99.263
Max. virtual memory (cumulated for all children) (KiB): 4772

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.080987
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 628
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= 12
involuntary context switches= 2

runsolver used 0.001999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node39 on Mon Apr 30 17:08:41 UTC 2007

IDJOB= 433015
IDBENCH= 2156
IDSOLVER= 199
FILE ID= node39/433015-1177952921

PBS_JOBID= 4727606

Free space on /tmp= 66558 MiB

SOLVER NAME= bsolo 3.0.17
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-ssa2670-141.opb
COMMAND LINE= bsolo3.0.17 -m1800 /tmp/evaluation/433015-1177952921/instance-433015-1177952921.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node39/watcher-433015-1177952921 -o ROOT/results/node39/solver-433015-1177952921 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.17 -m1800 /tmp/evaluation/433015-1177952921/instance-433015-1177952921.opb            

META MD5SUM SOLVER= c9b15312c639dd71a11a1e3ca1b27020
MD5SUM BENCH=  bf686e12342472d00013af54a5ee9279

RANDOM SEED= 88240003

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node39.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.256
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.256
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:       1711432 kB
Buffers:         41776 kB
Cached:         208468 kB
SwapCached:      13868 kB
Active:         142228 kB
Inactive:       132000 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1711432 kB
SwapTotal:     4192956 kB
SwapFree:      4159396 kB
Dirty:            6856 kB
Writeback:           0 kB
Mapped:          31072 kB
Slab:            55572 kB
Committed_AS:  2146856 kB
PageTables:       2012 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= 66558 MiB

End job on node39 on Mon Apr 30 17:08:42 UTC 2007