Trace number 2669222

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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/CT 0.1UNSAT 0.469927 0.469753

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-bf2670-001.opb
MD5SUM7ecb3834576c61e36b2048d581937745
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.066989
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables2786
Total number of constraints4827
Number of constraints which are clauses4827
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 2786
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 2786
Number of bits of the sum of numbers in the objective function 12
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 2786
Number of bits of the biggest sum of numbers12
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.00/0.00	c PB/CT 0.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.04/0.06	c constraints 0/0 clauses 4151/0 units 336
0.04/0.06	c vars 2786
0.04/0.07	c objective 2611 + 85
0.29/0.36	c 0.32395 32.5117 15 79
0.39/0.46	s UNSATISFIABLE

Verifier Data 

ERROR: no interpretation found !

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2669222-1276446023/watcher-2669222-1276446023 -o /tmp/evaluation-result-2669222-1276446023/solver-2669222-1276446023 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2669222-1276446023.opb 

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): 2000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 25386
/proc/meminfo: memFree=1840128/2059040 swapFree=4136716/4192956
[pid=25386] ppid=25384 vsize=2488 CPUtime=0
/proc/25386/stat : 25386 (pbct) R 25384 25386 25192 0 -1 4202496 311 0 0 0 0 0 0 0 20 0 1 0 20203867 2547712 234 1992294400 134512640 136485738 4294191840 18446744073709551615 135332318 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/25386/statm: 622 234 157 482 0 138 0

[startup+0.0466809 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 25386
/proc/meminfo: memFree=1840128/2059040 swapFree=4136716/4192956
[pid=25386] ppid=25384 vsize=2488 CPUtime=0.04
/proc/25386/stat : 25386 (pbct) R 25384 25386 25192 0 -1 4202496 332 0 0 0 4 0 0 0 20 0 1 0 20203867 2547712 255 1992294400 134512640 136485738 4294191840 18446744073709551615 134540771 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/25386/statm: 622 255 157 482 0 138 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 2488

[startup+0.10169 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 25386
/proc/meminfo: memFree=1840128/2059040 swapFree=4136716/4192956
[pid=25386] ppid=25384 vsize=6716 CPUtime=0.09
/proc/25386/stat : 25386 (pbct) R 25384 25386 25192 0 -1 4202496 1346 0 0 0 9 0 0 0 20 0 1 0 20203867 6877184 1269 1992294400 134512640 136485738 4294191840 18446744073709551615 134659008 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/25386/statm: 1679 1271 194 482 0 1195 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6716

[startup+0.301725 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 25386
/proc/meminfo: memFree=1840128/2059040 swapFree=4136716/4192956
[pid=25386] ppid=25384 vsize=32036 CPUtime=0.29
/proc/25386/stat : 25386 (pbct) R 25384 25386 25192 0 -1 4202496 7773 0 0 0 26 3 0 0 20 0 1 0 20203867 32804864 7501 1992294400 134512640 136485738 4294191840 18446744073709551615 134929217 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/25386/statm: 8009 7501 210 482 0 7525 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 32036

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

[startup+0.401744 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 25386
/proc/meminfo: memFree=1840128/2059040 swapFree=4136716/4192956
[pid=25386] ppid=25384 vsize=32052 CPUtime=0.39
/proc/25386/stat : 25386 (pbct) R 25384 25386 25192 0 -1 4202496 8121 0 0 0 36 3 0 0 20 0 1 0 20203867 32821248 7561 1992294400 134512640 136485738 4294191840 18446744073709551615 135839931 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/25386/statm: 8013 7561 247 482 0 7529 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 32052

Child status: 0
Real time (s): 0.469753
CPU time (s): 0.469927
CPU user time (s): 0.429934
CPU system time (s): 0.039993
CPU usage (%): 100.037
Max. virtual memory (cumulated for all children) (KiB): 32052

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.429934
system time used= 0.039993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8122
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= 1
involuntary context switches= 2

runsolver used 0.004999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node012 at 2010-06-13 18:20:23
IDJOB=2669222
IDBENCH=2103
IDSOLVER=1170
FILE ID=node012/2669222-1276446023
PBS_JOBID= 11173332
Free space on /tmp= 62412 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-bf2670-001.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2669222-1276446023/watcher-2669222-1276446023 -o /tmp/evaluation-result-2669222-1276446023/solver-2669222-1276446023 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2669222-1276446023.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 7ecb3834576c61e36b2048d581937745
RANDOM SEED=1636734110

node012.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.258
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.51
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.258
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.45
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1840656 kB
Buffers:         20644 kB
Cached:         120316 kB
SwapCached:       9228 kB
Active:          64264 kB
Inactive:        88932 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1840656 kB
SwapTotal:     4192956 kB
SwapFree:      4136716 kB
Dirty:            2276 kB
Writeback:           0 kB
AnonPages:       10856 kB
Mapped:           9224 kB
Slab:            43452 kB
PageTables:       4024 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182048 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62408 MiB
End job on node012 at 2010-06-13 18:20:24