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

Namemps-v2-13-7/ftp.netlib.org/lp/data/normalized-mps-v2-13-7-sctap2.opb
MD5SUMc56066a13a725fcc9c143db3d9f8cc06
Bench Categoryoptimization, medium integers (OPTMEDINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 63774720
Optimality of the best value was proved NO
Number of terms in the objective function 28200
Biggest coefficient in the objective function 41943040
Number of bits for the biggest coefficient in the objective function 26
Sum of the numbers in the objective function 25763487750
Number of bits of the sum of numbers in the objective function 35
Biggest number in a constraint 41943040
Number of bits of the biggest number in a constraint 26
Biggest sum of numbers in a constraint 25763487750
Number of bits of the biggest sum of numbers35
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark1204.69
Number of variables37600
Total number of constraints1090
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1090
Minimum length of a constraint60
Maximum length of a constraint480

Trace number 8361

Launcher Data

LAUNCH ON wulflinc11 THE 2005-09-20 16:23:26 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=5539 boxname=wulflinc11 idbench=851 idsolver=5 numberseed=0
MD5SUM SOLVER: 104a539e9cf344a86ca96d2c957e7d7f  /oldhome/oroussel/solvers/Pueblo
MD5SUM BENCH:  c56066a13a725fcc9c143db3d9f8cc06  /oldhome/oroussel/tmp/wulflinc11/normalized-mps-v2-13-7-sctap2.opb
REAL COMMAND:  Pueblo
IDLAUNCH: 5539
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.028
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.028
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:        820772 kB
Buffers:         33856 kB
Cached:         153112 kB
SwapCached:        916 kB
Active:          97964 kB
Inactive:        91636 kB
HighTotal:      131008 kB
HighFree:         1680 kB
LowTotal:       903652 kB
LowFree:        819092 kB
SwapTotal:     2097136 kB
SwapFree:      2095640 kB
Dirty:               4 kB
Writeback:           0 kB
Mapped:           5684 kB
Slab:            18696 kB
Committed_AS:    64172 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-20 16:23:29 (client local time) WITH STATUS 0 IN 2.66659 SECONDS
stats: 5539 7 2.66659 0

Solver Data

c Pueblo version 1.3 (July 2005)
c Developed @ University of Michigan, Ann Arbor, MI
c  by Hossein Sheini
c sum of numeric constants out of range [1]
s UNKNOWN

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/6838/stat): 6838 (Pueblo) R 6837 6838 9854 0 -1 0 19 0 0 0 0 0 0 0 19 0 1 0 1801717360 167936 3 4294967295 134512640 134578447 3221224624 3221224624 1073744960 0 0 5 0 0 0 0 17 1 0 0
Raw data (/proc/6838/statm): 41 3 40 18 0 23 0
[pid=6838] vsize: 164
open syscall for file /etc/ld.so.preload
open syscall for file tls/i686/mmx/libstdc++.so.5
open syscall for file tls/i686/libstdc++.so.5
open syscall for file tls/mmx/libstdc++.so.5
open syscall for file tls/libstdc++.so.5
open syscall for file i686/mmx/libstdc++.so.5
open syscall for file i686/libstdc++.so.5
open syscall for file mmx/libstdc++.so.5
open syscall for file libstdc++.so.5
open syscall for file /oldhome/oroussel/lib/tls/i686/mmx/libstdc++.so.5
open syscall for file /oldhome/oroussel/lib/tls/i686/libstdc++.so.5
open syscall for file /oldhome/oroussel/lib/tls/mmx/libstdc++.so.5
open syscall for file /oldhome/oroussel/lib/tls/libstdc++.so.5
open syscall for file /oldhome/oroussel/lib/i686/mmx/libstdc++.so.5
open syscall for file /oldhome/oroussel/lib/i686/libstdc++.so.5
open syscall for file /oldhome/oroussel/lib/mmx/libstdc++.so.5
open syscall for file /oldhome/oroussel/lib/libstdc++.so.5
open syscall for file /etc/ld.so.cache
open syscall for file /usr/lib/libstdc++.so.5
open syscall for file tls/i686/mmx/libm.so.6
open syscall for file tls/i686/libm.so.6
open syscall for file tls/mmx/libm.so.6
open syscall for file tls/libm.so.6
open syscall for file i686/mmx/libm.so.6
open syscall for file i686/libm.so.6
open syscall for file mmx/libm.so.6
open syscall for file libm.so.6
open syscall for file /oldhome/oroussel/lib/libm.so.6
open syscall for file /lib/tls/libm.so.6
open syscall for file tls/i686/mmx/libgcc_s.so.1
open syscall for file tls/i686/libgcc_s.so.1
open syscall for file tls/mmx/libgcc_s.so.1
open syscall for file tls/libgcc_s.so.1
open syscall for file i686/mmx/libgcc_s.so.1
open syscall for file i686/libgcc_s.so.1
open syscall for file mmx/libgcc_s.so.1
open syscall for file libgcc_s.so.1
open syscall for file /oldhome/oroussel/lib/libgcc_s.so.1
open syscall for file /lib/libgcc_s.so.1
open syscall for file tls/i686/mmx/libc.so.6
open syscall for file tls/i686/libc.so.6
open syscall for file tls/mmx/libc.so.6
open syscall for file tls/libc.so.6
open syscall for file i686/mmx/libc.so.6
open syscall for file i686/libc.so.6
open syscall for file mmx/libc.so.6
open syscall for file libc.so.6
open syscall for file /oldhome/oroussel/lib/libc.so.6
open syscall for file /lib/tls/libc.so.6
One traced child (pid=6838) exited with status: 0
All traced children have exited ! Game is over.

Child status: 0
Real time (s): 2.72754
CPU time (s): 2.66659
CPU user time (s): 2.55661
CPU system time (s): 0.109983
CPU usage (%): 97.7655
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

ERROR: no interpretation found !