Trace number 2669161

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.1Wrong UNSAT 0.491924 0.4922

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/mps-v2-20-10/
MIPLIB/miplib/normalized-mps-v2-20-10-lp4l.opb
MD5SUM8d2c17131f0dd6c2b5d472cf1eef4c89
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark2967
Best CPU time to get the best result obtained on this benchmark0.557914
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2967
Optimality of the best value was proved YES
Number of variables1086
Total number of constraints85
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)84
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint4
Maximum length of a constraint1086
Number of terms in the objective function 1086
Biggest coefficient in the objective function 283
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 197191
Number of bits of the sum of numbers in the objective function 18
Biggest number in a constraint 283
Number of bits of the biggest number in a constraint 9
Biggest sum of numbers in a constraint 197191
Number of bits of the biggest sum of numbers18
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.00/0.01	c constraints 85/0 clauses 0/0 units 0
0.00/0.01	c vars 1086
0.00/0.01	c objective 1086 + 0
0.29/0.37	c 0.331949 27.7461 0 0
0.39/0.48	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-2669161-1276437381/watcher-2669161-1276437381 -o /tmp/evaluation-result-2669161-1276437381/solver-2669161-1276437381 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2669161-1276437381.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.99 0.97 0.99 3/106 23093
/proc/meminfo: memFree=1870780/2059040 swapFree=4140228/4192956
[pid=23093] ppid=23091 vsize=2352 CPUtime=0
/proc/23093/stat : 23093 (pbct) R 23091 23093 21207 0 -1 4202496 303 0 0 0 0 0 0 0 20 0 1 0 19339839 2408448 226 1992294400 134512640 136485738 4291071888 18446744073709551615 135850441 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/23093/statm: 588 226 156 482 0 104 0

[startup+0.0798071 s]
/proc/loadavg: 0.99 0.97 0.99 3/106 23093
/proc/meminfo: memFree=1870780/2059040 swapFree=4140228/4192956
[pid=23093] ppid=23091 vsize=8052 CPUtime=0.07
/proc/23093/stat : 23093 (pbct) R 23091 23093 21207 0 -1 4202496 1679 0 0 0 7 0 0 0 20 0 1 0 19339839 8245248 1602 1992294400 134512640 136485738 4291071888 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/23093/statm: 2013 1603 197 482 0 1529 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 8052

[startup+0.100809 s]
/proc/loadavg: 0.99 0.97 0.99 3/106 23093
/proc/meminfo: memFree=1870780/2059040 swapFree=4140228/4192956
[pid=23093] ppid=23091 vsize=9108 CPUtime=0.09
/proc/23093/stat : 23093 (pbct) R 23091 23093 21207 0 -1 4202496 1978 0 0 0 8 1 0 0 20 0 1 0 19339839 9326592 1901 1992294400 134512640 136485738 4291071888 18446744073709551615 135848659 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/23093/statm: 2277 1902 197 482 0 1793 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9108

[startup+0.300832 s]
/proc/loadavg: 0.99 0.97 0.99 3/106 23093
/proc/meminfo: memFree=1870780/2059040 swapFree=4140228/4192956
[pid=23093] ppid=23091 vsize=26532 CPUtime=0.29
/proc/23093/stat : 23093 (pbct) R 23091 23093 21207 0 -1 4202496 6364 0 0 0 26 3 0 0 20 0 1 0 19339839 27168768 6123 1992294400 134512640 136485738 4291071888 18446744073709551615 134833685 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/23093/statm: 6633 6123 210 482 0 6149 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 26532

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

[startup+0.400843 s]
/proc/loadavg: 0.99 0.97 0.99 3/106 23093
/proc/meminfo: memFree=1870780/2059040 swapFree=4140228/4192956
[pid=23093] ppid=23091 vsize=26956 CPUtime=0.39
/proc/23093/stat : 23093 (pbct) R 23091 23093 21207 0 -1 4202496 6852 0 0 0 36 3 0 0 20 0 1 0 19339839 27602944 6287 1992294400 134512640 136485738 4291071888 18446744073709551615 135839911 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/23093/statm: 6739 6287 244 482 0 6255 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 26956

Child status: 0
Real time (s): 0.4922
CPU time (s): 0.491924
CPU user time (s): 0.449931
CPU system time (s): 0.041993
CPU usage (%): 99.9439
Max. virtual memory (cumulated for all children) (KiB): 26956

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.449931
system time used= 0.041993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 6853
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.008998 second system time

The end

Launcher Data

Begin job on node009 at 2010-06-13 15:56:21
IDJOB=2669161
IDBENCH=1856
IDSOLVER=1170
FILE ID=node009/2669161-1276437381
PBS_JOBID= 11173311
Free space on /tmp= 62444 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/mps-v2-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-lp4l.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2669161-1276437381/watcher-2669161-1276437381 -o /tmp/evaluation-result-2669161-1276437381/solver-2669161-1276437381 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2669161-1276437381.opb

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

MD5SUM BENCH= 8d2c17131f0dd6c2b5d472cf1eef4c89
RANDOM SEED=1450668417

node009.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.199
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.39
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.199
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.44
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1871184 kB
Buffers:          6460 kB
Cached:         104004 kB
SwapCached:       5328 kB
Active:          23244 kB
Inactive:        99324 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1871184 kB
SwapTotal:     4192956 kB
SwapFree:      4140228 kB
Dirty:            2048 kB
Writeback:           0 kB
AnonPages:       10976 kB
Mapped:          12944 kB
Slab:            43420 kB
PageTables:       4052 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180580 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= 62440 MiB
End job on node009 at 2010-06-13 15:56:21