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 in four parts:
  1. 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 provide some useful information on the computer.
  2. 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 !
  3. 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 1200 seconds. 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 1230 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (900Mb).
    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.
  4. 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.

General information on the benchmark

Namesubmitted/manquinho/primes-dimacs-cnf/normalized-bf2670-001.opb
MD5SUMcaacddb078d9307989a3c2624242ecb4
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of terms in the objective function 2786
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 2786
Number of bits of the sum of numbers in the objective function 12
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 2786
Number of bits of the biggest sum of numbers12
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.185971
Number of variables2786
Total number of constraints4827
Number of constraints which are clauses4827
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

Trace number 2330

Launcher Data

LAUNCH ON wulflinc5 THE 2005-09-18 19:16:22 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=3735 boxname=wulflinc5 idbench=219 idsolver=4 numberseed=0
MD5SUM SOLVER: 21c3ffd7205c96d5f0784fd273b92938  /oldhome/oroussel/solvers/PBS4
MD5SUM BENCH:  caacddb078d9307989a3c2624242ecb4  /oldhome/oroussel/tmp/wulflinc5/normalized-bf2670-001.opb
REAL COMMAND:  PBS4 /oldhome/oroussel/tmp/wulflinc5/normalized-bf2670-001.opb
IDLAUNCH: 3735
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.007
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 888.83

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.007
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 899.07

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        916712 kB
Buffers:         34352 kB
Cached:          59864 kB
SwapCached:        780 kB
Active:          61848 kB
Inactive:        35156 kB
HighTotal:      131008 kB
HighFree:        67452 kB
LowTotal:       903652 kB
LowFree:        849260 kB
SwapTotal:     2097136 kB
SwapFree:      2095888 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5804 kB
Slab:            15484 kB
Committed_AS:    64264 kB
PageTables:        332 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-18 19:16:23 (client local time) WITH STATUS 20 IN 0.691894 SECONDS
stats: 3735 7 0.691894 20

Solver Data

c PBS v4 by Bashar Al-Rawi & Fadi Aloul
c Solving /oldhome/oroussel/tmp/wulflinc5/normalized-bf2670-001.opb ......
s UNSATISFIABLE
c Done, CPU Time=0.19497

Watcher Data

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGTERM then SIGKILL): 921600 Kb
Enforcing VSIZE limit: 994918400 bytes
Current StackSize limit: 67108864 bytes
Raw data (/proc/12904/stat): 12904 (PBS4) R 12903 12904 824 0 -1 0 18 0 0 0 0 0 0 0 23 0 1 0 1785481637 978944 2 4294967295 134512640 135450776 3221224576 3221224576 134512960 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/12904/statm): 239 2 232 232 0 7 0
[pid=12904] vsize: 956
open syscall for file /dev/null
open syscall for file /oldhome/oroussel/tmp/wulflinc5/normalized-bf2670-001.opb
open syscall for file /oldhome/oroussel/tmp/wulflinc5/normalized-bf2670-001.opb
One traced child (pid=12904) exited with status: 20
All traced children have exited ! Game is over.

Child status: 20
Real time (s): 0.701545
CPU time (s): 0.691894
CPU user time (s): 0.680896
CPU system time (s): 0.010998
CPU usage (%): 98.6243
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

ERROR: no interpretation found !