Trace number 457471

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-10UNSAT 0.042993 0.037032

General information on the benchmark

Namenormalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/
manquinho/dbsg/normalized-dbsg_10_4_2_5.opb
MD5SUM76be868a9238ea0681c7ac98a4cfcbe5
Bench CategorySATUNSAT-SMALLINT-NLC (no optimisation, small integers, non 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.005999
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables20
Total number of constraints32
Number of constraints which are clauses10
Number of constraints which are cardinality constraints (but not clauses)1
Number of constraints which are nor clauses,nor cardinality constraints21
Minimum length of a constraint2
Maximum length of a constraint20
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 5
Number of bits of the biggest number in a constraint 3
Biggest sum of numbers in a constraint 20
Number of bits of the biggest sum of numbers5
Number of products (including duplicates)96
Sum of products size (including duplicates)192
Number of different products48
Sum of products size96

Solver Data (download as text)

0.00/0.03	s UNSATISFIABLE

Verifier Data (download as text)

ERROR: no interpretation found !

Conversion Script Data (download as text)

Linearizing /tmp/evaluation/457471-1178369298/instance-457471-1178369298.opb

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node70/watcher-457471-1178369298 -o ROOT/results/node70/solver-457471-1178369298 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-457471-1178369298.opb /tmp/evaluation/457471-1178369298/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.92 1.01 0.95 3/64 16757
/proc/meminfo: memFree=1738200/2055920 swapFree=4183864/4192956
[pid=16757] ppid=16755 vsize=12268 CPUtime=0
/proc/16757/stat : 16757 (pbclasp) D 16755 16757 15217 0 -1 4194304 350 0 0 0 0 0 0 0 18 0 1 0 276467165 12562432 317 18446744073709551615 4194304 4206940 548682069264 18446744073709551615 233402235493 0 2147483391 4224 0 18446744072099781622 0 0 17 1 0 0
/proc/16757/statm: 3067 317 242 3 0 167 0

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

Child status: 0
Real time (s): 0.037032
CPU time (s): 0.042993
CPU user time (s): 0.029995
CPU system time (s): 0.012998
CPU usage (%): 116.097
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.029995
system time used= 0.012998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2148
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= 51
involuntary context switches= 6

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node70 on Sat May  5 12:48:18 UTC 2007

IDJOB= 457471
IDBENCH= 48343
IDSOLVER= 167
FILE ID= node70/457471-1178369298

PBS_JOBID= 5189160

Free space on /tmp= 66564 MiB

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

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

META MD5SUM SOLVER= 1e5f480786d97be718f2223f2ffb5f36
MD5SUM BENCH=  76be868a9238ea0681c7ac98a4cfcbe5

RANDOM SEED= 876220805

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node70.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 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.218
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.218
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:       1738800 kB
Buffers:         30764 kB
Cached:         191252 kB
SwapCached:       3132 kB
Active:          60340 kB
Inactive:       172076 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1738800 kB
SwapTotal:     4192956 kB
SwapFree:      4183864 kB
Dirty:             668 kB
Writeback:           0 kB
Mapped:          16344 kB
Slab:            70808 kB
Committed_AS:  7569572 kB
PageTables:       1400 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66564 MiB

End job on node70 on Sat May  5 12:48:18 UTC 2007