Trace number 364054

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 NameAnswerObjective functionCPU timeWall clock time
PB-clasp 2007-03-23UNSAT 0.229964 0.232122

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-ssa0432-003.opb
MD5SUM7eae448a5d260ba3e367d5a8053e4a27
Bench CategoryOPT-SMALLINT (optimisation, small integers)
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.018996
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables870
Total number of constraints1462
Number of constraints which are clauses1462
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 constraint1
Maximum length of a constraint5
Number of terms in the objective function 870
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 870
Number of bits of the sum of numbers in the objective function 10
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 870
Number of bits of the biggest sum of numbers10
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.11/0.23	s UNSATISFIABLE

Verifier Data (download as text)

ERROR: no interpretation found !

Conversion Script Data (download as text)

/tmp/evaluation/364054-1177036875/instance-364054-1177036875.opb is already a linear file

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node62/watcher-364054-1177036875 -o ROOT/results/node62/solver-364054-1177036875 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-364054-1177036875.opb /tmp/evaluation/364054-1177036875/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.90 1.01 0.99 3/64 28829
/proc/meminfo: memFree=1806448/2055920 swapFree=4184556/4192956
[pid=28829] ppid=28827 vsize=12268 CPUtime=0
/proc/28829/stat : 28829 (pbclasp) D 28827 28829 27276 0 -1 4194304 351 0 0 0 0 0 0 0 18 0 1 0 22263615 12562432 317 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 236437863013 0 2147483391 4224 0 18446744072099781622 0 0 17 1 0 0
/proc/28829/statm: 3067 317 242 3 0 167 0

[startup+0.029592 s]
/proc/loadavg: 0.90 1.01 0.99 3/64 28829
/proc/meminfo: memFree=1806448/2055920 swapFree=4184556/4192956
[pid=28829] ppid=28827 vsize=12664 CPUtime=0.01
/proc/28829/stat : 28829 (pbclasp) S 28827 28829 27276 0 -1 4194304 542 0 0 0 1 0 0 0 16 0 1 0 22263615 12967936 494 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 236446593122 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/28829/statm: 3166 494 324 3 0 266 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 12664

[startup+0.101599 s]
/proc/loadavg: 0.90 1.01 0.99 3/64 28829
/proc/meminfo: memFree=1806448/2055920 swapFree=4184556/4192956
[pid=28829] ppid=28827 vsize=12664 CPUtime=0.01
/proc/28829/stat : 28829 (pbclasp) S 28827 28829 27276 0 -1 4194304 542 0 0 0 1 0 0 0 16 0 1 0 22263615 12967936 494 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 236446593122 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/28829/statm: 3166 494 324 3 0 266 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 12664

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

[startup+0.201614 s]
/proc/loadavg: 0.90 1.01 0.99 3/64 28829
/proc/meminfo: memFree=1806448/2055920 swapFree=4184556/4192956
[pid=28829] ppid=28827 vsize=12660 CPUtime=0.11
/proc/28829/stat : 28829 (pbclasp) S 28827 28829 27276 0 -1 4194304 671 1589 0 0 1 0 10 0 16 0 1 0 22263615 12963840 533 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 236446597012 0 0 4230 16384 18446744071563356171 0 0 17 0 0 0
/proc/28829/statm: 3165 533 343 3 0 265 0
Current children cumulated CPU time (s) 0.11
Current children cumulated vsize (KiB) 12660

Child status: 0
Real time (s): 0.232122
CPU time (s): 0.229964
CPU user time (s): 0.204968
CPU system time (s): 0.024996
CPU usage (%): 99.0703
Max. virtual memory (cumulated for all children) (KiB): 12664

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.204968
system time used= 0.024996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3649
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= 92
involuntary context switches= 10

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node62 on Fri Apr 20 02:41:15 UTC 2007

IDJOB= 364054
IDBENCH= 2061
IDSOLVER= 158
FILE ID= node62/364054-1177036875

PBS_JOBID= 4630645

Free space on /tmp= 66497 MiB

SOLVER NAME= PB-clasp 2007-03-23
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-ssa0432-003.opb
COMMAND LINE= pbclasp instance-364054-1177036875.opb /tmp/evaluation/364054-1177036875/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node62/convwatcher-364054-1177036875 -o ROOT/results/node62/conversion-364054-1177036875 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/364054-1177036875/instance-364054-1177036875.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 814f1745fa20958d8b352781cfa0403e
MD5SUM BENCH=  7eae448a5d260ba3e367d5a8053e4a27

RANDOM SEED= 196940621

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node62.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.216
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.216
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:       1806920 kB
Buffers:         22492 kB
Cached:         155968 kB
SwapCached:       2148 kB
Active:          47872 kB
Inactive:       140696 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1806920 kB
SwapTotal:     4192956 kB
SwapFree:      4184556 kB
Dirty:            1180 kB
Writeback:           0 kB
Mapped:          16456 kB
Slab:            46388 kB
Committed_AS:  1026576 kB
PageTables:       1464 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= 66497 MiB

End job on node62 on Fri Apr 20 02:41:17 UTC 2007