Trace number 456961

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-clasp 2007-04-10SAT 0.31895 0.288107

General information on the benchmark

Namenormalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/
manquinho/dbsg/normalized-dbsg_100_10_1_15.opb
MD5SUM29dd42e0067afa72a17cd46c1f9628e9
Bench CategorySATUNSAT-SMALLINT-NLC (no optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.05599
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables200
Total number of constraints302
Number of constraints which are clauses100
Number of constraints which are cardinality constraints (but not clauses)1
Number of constraints which are nor clauses,nor cardinality constraints201
Minimum length of a constraint2
Maximum length of a constraint200
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 15
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 200
Number of bits of the biggest sum of numbers8
Number of products (including duplicates)2496
Sum of products size (including duplicates)4992
Number of different products1248
Sum of products size2496

Solver Data (download as text)

0.00/0.28	s SATISFIABLE
0.00/0.28	v x4 x5 x6 x11 x24 x28 x34 x48 x49 x54 x57 x64 x75 x76 x83 x85 x92 x99 x101 x110 x112 x114 x117 x131 x142 x144 x150 x155 x159 x160 x169
0.00/0.28	v x170 x177 x180 x189 x197 x290 x322 x356 x494 x502 x797 x862 x972 x1172 x1187 x1212 x1265 x1364 x1392

Verifier Data (download as text)

OK	0

Conversion Script Data (download as text)

Linearizing /tmp/evaluation/456961-1178365026/instance-456961-1178365026.opb

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node76/watcher-456961-1178365026 -o ROOT/results/node76/solver-456961-1178365026 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-456961-1178365026.opb /tmp/evaluation/456961-1178365026/temp 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.91 0.95 0.90 3/69 6422
/proc/meminfo: memFree=1519984/2055888 swapFree=4087212/4096564
[pid=6422] ppid=6420 vsize=12272 CPUtime=0
/proc/6422/stat : 6422 (pbclasp) R 6420 6422 5683 0 -1 4194304 346 0 0 0 0 0 0 0 18 0 1 0 284417179 12566528 315 18446744073709551615 4194304 4206940 548682069264 18446744073709551615 206843904885 0 0 4224 0 0 0 0 17 1 0 0
/proc/6422/statm: 3068 315 240 3 0 167 0

[startup+0.072733 s]
/proc/loadavg: 0.91 0.95 0.90 3/69 6422
/proc/meminfo: memFree=1519984/2055888 swapFree=4087212/4096564
[pid=6422] ppid=6420 vsize=12404 CPUtime=0
/proc/6422/stat : 6422 (pbclasp) S 6420 6422 5683 0 -1 4194304 493 0 0 0 0 0 0 0 16 0 1 0 284417179 12701696 444 18446744073709551615 4194304 4206940 548682069264 18446744073709551615 206852632722 0 0 4224 16384 18446744071563651996 0 0 17 1 0 0
/proc/6422/statm: 3101 444 318 3 0 200 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12404

[startup+0.101733 s]
/proc/loadavg: 0.91 0.95 0.90 3/69 6422
/proc/meminfo: memFree=1519984/2055888 swapFree=4087212/4096564
[pid=6422] ppid=6420 vsize=12404 CPUtime=0
/proc/6422/stat : 6422 (pbclasp) S 6420 6422 5683 0 -1 4194304 493 0 0 0 0 0 0 0 16 0 1 0 284417179 12701696 444 18446744073709551615 4194304 4206940 548682069264 18446744073709551615 206852632722 0 0 4224 16384 18446744071563651996 0 0 17 1 0 0
/proc/6422/statm: 3101 444 318 3 0 200 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12404

Solver just ended. Dumping a history of the last processes samples

[startup+0.201753 s]
/proc/loadavg: 0.91 0.95 0.90 3/69 6422
/proc/meminfo: memFree=1519984/2055888 swapFree=4087212/4096564
[pid=6422] ppid=6420 vsize=12404 CPUtime=0
/proc/6422/stat : 6422 (pbclasp) S 6420 6422 5683 0 -1 4194304 493 0 0 0 0 0 0 0 16 0 1 0 284417179 12701696 444 18446744073709551615 4194304 4206940 548682069264 18446744073709551615 206852632722 0 0 4224 16384 18446744071563651996 0 0 17 1 0 0
/proc/6422/statm: 3101 444 318 3 0 200 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12404

Child status: 0
Real time (s): 0.288107
CPU time (s): 0.31895
CPU user time (s): 0.304953
CPU system time (s): 0.013997
CPU usage (%): 110.705
Max. virtual memory (cumulated for all children) (KiB): 12404

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.304953
system time used= 0.013997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2632
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 83
involuntary context switches= 13

runsolver used 0.001999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node76 on Sat May  5 11:37:06 UTC 2007

IDJOB= 456961
IDBENCH= 48309
IDSOLVER= 167
FILE ID= node76/456961-1178365026

PBS_JOBID= 5189155

Free space on /tmp= 66651 MiB

SOLVER NAME= PB-clasp 2007-04-10
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/manquinho/dbsg/normalized-dbsg_100_10_1_15.opb
COMMAND LINE= pbclasp instance-456961-1178365026.opb /tmp/evaluation/456961-1178365026/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node76/convwatcher-456961-1178365026 -o ROOT/results/node76/conversion-456961-1178365026 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/456961-1178365026/instance-456961-1178365026.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-456961-1178365026 -o ROOT/results/node76/solver-456961-1178365026 -C 1800 -W 3600 -M 1800 --output-limit 1,15  pbclasp instance-456961-1178365026.opb /tmp/evaluation/456961-1178365026/temp

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  29dd42e0067afa72a17cd46c1f9628e9

RANDOM SEED= 640902668

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node76.alineos.net 2.6.9-34.ELsmp #1 SMP Thu Mar 9 06:23:23 GMT 2006 x86_64 x86_64 x86_64 GNU/Linux

/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.277
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	: 6006.17
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.277
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1520328 kB
Buffers:         36776 kB
Cached:         399792 kB
SwapCached:       3052 kB
Active:         154840 kB
Inactive:       293640 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1520328 kB
SwapTotal:     4096564 kB
SwapFree:      4087212 kB
Dirty:             576 kB
Writeback:           0 kB
Mapped:          17796 kB
Slab:            73464 kB
Committed_AS:  5737068 kB
PageTables:       1432 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66651 MiB

End job on node76 on Sat May  5 11:37:07 UTC 2007