Trace number 33711

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
PB-smodels 1.28UNSAT 3.10853 2.18543

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-cache.inv10.ucl.opb
MD5SUM449faf6379a77b0035cc1474243ef90a
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.274957
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables8937
Total number of constraints26319
Number of constraints which are clauses26047
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints272
Minimum length of a constraint1
Maximum length of a constraint9
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 17
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 62
Number of bits of the biggest sum of numbers6
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 Running pbsmodels-v1.28
2.18	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

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

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node70/watcher-33711-1149623326 -o ROOT/results/node70/solver-33711-1149623326 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node70/33711-1149623326/instance-33711-1149623326.opb 484554908 ROOT/tmp/node70/33711-1149623326 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.95 0.90 2/64 5679
/proc/meminfo: memFree=1558880/2055920 swapFree=4182220/4192956
[pid=5679] ppid=5677 vsize=5360 CPUtime=0
/proc/5679/stat : 5679 (runpbsmodels) S 5677 5679 5633 0 -1 4194304 286 0 0 0 0 0 0 0 19 0 1 0 228002182 5488640 234 18446744073709551615 4194304 4889804 548682069168 18446744073709551615 233402065732 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/5679/statm: 1340 234 195 169 0 51 0
[pid=5680] ppid=5679 vsize=0 CPUtime=0
/proc/5680/stat : 5680 (runpbsmodels) R 5679 5679 5633 0 -1 4194368 18 0 0 0 0 0 0 0 20 0 1 0 228002182 0 0 18446744073709551615 0 0 0 18446744073709551615 233402068263 0 0 4096 0 0 0 0 17 1 0 0
/proc/5680/statm: 6 2 0 0 0 1 0

Child status: 0
Real time (s): 2.18543
CPU time (s): 3.10853
CPU user time (s): 3.07653
CPU system time (s): 0.031995
CPU usage (%): 142.239
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node70 on Tue Jun  6 19:48:46 UTC 2006


FILE ID= 33711-1149623326

PBS_JOBID= 322530

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/web/uclid_pb_benchmarks/normalized-cache.inv10.ucl.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node70/33711-1149623326/instance-33711-1149623326.opb 484554908  ROOT/tmp/node70/33711-1149623326
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node70/watcher-33711-1149623326 -o ROOT/results/node70/solver-33711-1149623326 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels_solver-v1.28/runpbsmodels ROOT/tmp/node70/33711-1149623326/instance-33711-1149623326.opb 484554908  ROOT/tmp/node70/33711-1149623326

MD5SUM SOLVER= f639f6b7f53e3afd14340f75c0e271ee 82c14a26114306e436bf36ef1d1c85a0 c893ceb51a2aaa4ab2f96d97b043cdf0 8c810dcfce02286b111d075d14837741 79b233270d136fcdcf9d8f80d20efef0
MD5SUM BENCH=  449faf6379a77b0035cc1474243ef90a

RANDOM SEED= 484554908


/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.265
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.265
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:       1559216 kB
Buffers:         32968 kB
Cached:         388352 kB
SwapCached:       2388 kB
Active:          29800 kB
Inactive:       400132 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1559216 kB
SwapTotal:     4192956 kB
SwapFree:      4182220 kB
Dirty:             168 kB
Writeback:           0 kB
Mapped:          15400 kB
Slab:            52712 kB
Committed_AS:   364680 kB
PageTables:       1416 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node70 on Tue Jun  6 19:48:48 UTC 2006