Trace number 36268

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 NameAnswerCPU timeWall clock time
Pueblo 1.4UNSAT 0.159975 0.16831

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-blast-floppy1-8.ucl.opb
MD5SUMf8abb380dd08e138dce9720c80a7343a
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
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.118981
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables3618
Total number of constraints3931
Number of constraints which are clauses2865
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1066
Minimum length of a constraint1
Maximum length of a constraint25
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 7394
Number of bits of the biggest number in a constraint 13
Biggest sum of numbers in a constraint 19679
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 (download as text)

0.00	c Pueblo version 1.4 (September 2005)
0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
0.16	c starting to Solve
0.16	c #variables read: 3618 - #constraints read: 3930
0.16	c total time              : 0.15 s
0.16	s UNSATISFIABLE

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node15/watcher-36268-1149237086 -o ROOT/results/node15/solver-36268-1149237086 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node15/36268-1149237086/instance-36268-1149237086.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.63 0.89 0.96 2/64 28115
/proc/meminfo: memFree=1436888/2055920 swapFree=4181408/4192956
[pid=28115] ppid=28113 vsize=172 CPUtime=0
/proc/28115/stat : 28115 (Pueblo) R 28113 28115 28070 0 -1 4194304 38 0 0 0 0 0 0 0 19 0 1 0 189371397 176128 23 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 7512868 0 0 4096 0 0 0 0 17 1 0 0
/proc/28115/statm: 43 23 18 16 0 2 0

Child status: 20
Real time (s): 0.16831
CPU time (s): 0.159975
CPU user time (s): 0.154976
CPU system time (s): 0.004999
CPU usage (%): 95.0478
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node15 on Fri Jun  2 08:31:26 UTC 2006


FILE ID= 36268-1149237086

PBS_JOBID= 297090

BENCH NAME= ROOT/tmp/node15/36268-1149237086/instance-36268-1149237086.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node15/36268-1149237086/instance-36268-1149237086.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node15/watcher-36268-1149237086 -o ROOT/results/node15/solver-36268-1149237086 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node15/36268-1149237086/instance-36268-1149237086.opb

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  f8abb380dd08e138dce9720c80a7343a

RANDOM SEED= 660084814


/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.285
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.285
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:       1437096 kB
Buffers:         24224 kB
Cached:         534352 kB
SwapCached:       3308 kB
Active:          87860 kB
Inactive:       479460 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1437096 kB
SwapTotal:     4192956 kB
SwapFree:      4181408 kB
Dirty:             308 kB
Writeback:           0 kB
Mapped:          14680 kB
Slab:            37484 kB
Committed_AS:   233628 kB
PageTables:       1488 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node15 on Fri Jun  2 08:31:26 UTC 2006