Trace number 2669208

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.429934 0.430196

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-bf0432-007.opb
MD5SUM093787cffe9173c370b11fb5e77a5812
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.099984
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables2080
Total number of constraints4708
Number of constraints which are clauses4708
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 constraint6
Number of terms in the objective function 2080
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 2080
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 2080
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 4036/0 units 252
0.04/0.06	c vars 2080
0.04/0.06	c objective 1949 + 68
0.29/0.34	c 0.315951 27.1797 176 928
0.39/0.42	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-2669208-1276445093/watcher-2669208-1276445093 -o /tmp/evaluation-result-2669208-1276445093/solver-2669208-1276445093 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2669208-1276445093.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: 0.92 0.98 0.99 3/106 25126
/proc/meminfo: memFree=1834184/2059040 swapFree=4140384/4192956
[pid=25126] ppid=25124 vsize=2488 CPUtime=0
/proc/25126/stat : 25126 (pbct) R 25124 25126 24765 0 -1 4202496 309 0 0 0 0 0 0 0 20 0 1 0 20110959 2547712 231 1992294400 134512640 136485738 4294068512 18446744073709551615 135173296 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/25126/statm: 622 231 157 482 0 138 0

[startup+0.047868 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 25126
/proc/meminfo: memFree=1834184/2059040 swapFree=4140384/4192956
[pid=25126] ppid=25124 vsize=2488 CPUtime=0.04
/proc/25126/stat : 25126 (pbct) R 25124 25126 24765 0 -1 4202496 325 0 0 0 4 0 0 0 20 0 1 0 20110959 2547712 247 1992294400 134512640 136485738 4294068512 18446744073709551615 135416637 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/25126/statm: 622 247 157 482 0 138 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 2488

[startup+0.100879 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 25126
/proc/meminfo: memFree=1834184/2059040 swapFree=4140384/4192956
[pid=25126] ppid=25124 vsize=7128 CPUtime=0.09
/proc/25126/stat : 25126 (pbct) R 25124 25126 24765 0 -1 4202496 1449 0 0 0 9 0 0 0 20 0 1 0 20110959 7299072 1371 1992294400 134512640 136485738 4294068512 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/25126/statm: 1782 1372 194 482 0 1298 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7128

[startup+0.300921 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 25126
/proc/meminfo: memFree=1834184/2059040 swapFree=4140384/4192956
[pid=25126] ppid=25124 vsize=27828 CPUtime=0.29
/proc/25126/stat : 25126 (pbct) R 25124 25126 24765 0 -1 4202496 6722 0 0 0 27 2 0 0 20 0 1 0 20110959 28495872 6451 1992294400 134512640 136485738 4294068512 18446744073709551615 134874588 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/25126/statm: 6957 6451 225 482 0 6473 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 27828

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

[startup+0.400942 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 25126
/proc/meminfo: memFree=1834184/2059040 swapFree=4140384/4192956
[pid=25126] ppid=25124 vsize=26332 CPUtime=0.39
/proc/25126/stat : 25126 (pbct) R 25124 25126 24765 0 -1 4202496 6750 0 0 0 37 2 0 0 20 0 1 0 20110959 26963968 6158 1992294400 134512640 136485738 4294068512 18446744073709551615 134720175 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/25126/statm: 6583 6158 247 482 0 6099 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 26332

Child status: 0
Real time (s): 0.430196
CPU time (s): 0.429934
CPU user time (s): 0.399939
CPU system time (s): 0.029995
CPU usage (%): 99.9391
Max. virtual memory (cumulated for all children) (KiB): 27828

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

runsolver used 0.005999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node010 at 2010-06-13 18:04:53
IDJOB=2669208
IDBENCH=2073
IDSOLVER=1170
FILE ID=node010/2669208-1276445093
PBS_JOBID= 11173328
Free space on /tmp= 62500 MiB

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

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

MD5SUM BENCH= 093787cffe9173c370b11fb5e77a5812
RANDOM SEED=956138799

node010.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.267
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.53
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.267
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.46
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1834704 kB
Buffers:         27860 kB
Cached:         117324 kB
SwapCached:       6468 kB
Active:          63344 kB
Inactive:        95000 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1834704 kB
SwapTotal:     4192956 kB
SwapFree:      4140384 kB
Dirty:            2112 kB
Writeback:           0 kB
AnonPages:       10856 kB
Mapped:          13104 kB
Slab:            44148 kB
PageTables:       4028 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180952 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= 62496 MiB
End job on node010 at 2010-06-13 18:04:54