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/sorensson/garden/normalized-g2x2.opb
MD5SUM276f089932f6c452fdc3e3b93f688af7
Bench Categoryoptimization, small integers (OPTSMALLINT)
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2
Optimality of the best value was proved YES
Number of terms in the objective function 4
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 4
Number of bits of the sum of numbers in the objective function 3
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 4
Number of bits of the biggest sum of numbers3
Best result obtained on this benchmarkOPTIMUM FOUND
Best CPU time to get the best result obtained on this benchmark0.003998
Number of variables4
Total number of constraints4
Number of constraints which are clauses4
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 constraint3
Maximum length of a constraint3

Trace number 7772

Launcher Data

LAUNCH ON wulflinc12 THE 2005-09-20 14:18:00 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=4958 boxname=wulflinc12 idbench=270 idsolver=5 numberseed=0
MD5SUM SOLVER: 104a539e9cf344a86ca96d2c957e7d7f  /oldhome/oroussel/solvers/Pueblo
MD5SUM BENCH:  276f089932f6c452fdc3e3b93f688af7  /oldhome/oroussel/tmp/wulflinc12/normalized-g2x2.opb
REAL COMMAND:  Pueblo
IDLAUNCH: 4958
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 451.091
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.091
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:        891572 kB
Buffers:         34036 kB
Cached:          78420 kB
SwapCached:        492 kB
Active:          68556 kB
Inactive:        46452 kB
HighTotal:      131008 kB
HighFree:        50400 kB
LowTotal:       903652 kB
LowFree:        841172 kB
SwapTotal:     2097136 kB
SwapFree:      2096072 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:           5904 kB
Slab:            22380 kB
Committed_AS:    64168 kB
PageTables:        328 kB
VmallocTotal:   114680 kB
VmallocUsed:      1364 kB
VmallocChunk:   113256 kB
JOB ENDED THE 2005-09-20 14:18:01 (client local time) WITH STATUS 30 IN 0.010997 SECONDS
stats: 4958 0 0.010997 30

Solver Data

c Pueblo version 1.3 (July 2005)
c Developed @ University of Michigan, Ann Arbor, MI
c  by Hossein Sheini
c starting to Solve
c #variables read: 4 - #constraints read: 5
c optimum objective found = 2
c total time              : 0 s
s OPTIMUM FOUND
v -x1 -x2 x3 x4

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/19970/stat): 19970 (Pueblo) R 19969 19970 8263 0 -1 0 19 0 0 0 0 0 0 0 22 0 1 0 1800956323 167936 3 4294967295 134512640 134578447 3221224624 3221224624 1073744960 0 0 5 0 0 0 0 17 0 0 0
Raw data (/proc/19970/statm): 41 3 40 18 0 23 0
[pid=19970] 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=19970) exited with status: 30
All traced children have exited ! Game is over.

Child status: 30
Real time (s): 0.029722
CPU time (s): 0.010997
CPU user time (s): 0.003999
CPU system time (s): 0.006998
CPU usage (%): 36.9995
Max. virtual memory (cumulated for all children) (Kb): 0

Verifier Data

Verifier:	OK	2