Trace number 2684215

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.1 fixedUNSAT 0.32295 0.322494

General information on the benchmark

Name/OPT-BIGINT-LIN/leberre/opb-trendy/misc2010/
random/rand.newlist/normalized-randc5b1f2.cudf.trendy.opb
MD5SUM6aafe628c204287c66baba06106fbd9b
Bench CategoryOPT-BIGINT-LIN (optimisation, big integers, 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.32295
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables6597
Total number of constraints27303
Number of constraints which are clauses27036
Number of constraints which are cardinality constraints (but not clauses)267
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint553
Number of terms in the objective function 3110
Biggest coefficient in the objective function 3774555693
Number of bits for the biggest coefficient in the objective function 32
Sum of the numbers in the objective function 2083549895042
Number of bits of the sum of numbers in the objective function 41
Biggest number in a constraint 3774555693
Number of bits of the biggest number in a constraint 32
Biggest sum of numbers in a constraint 2083549895042
Number of bits of the biggest sum of numbers41
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.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.29/0.31	c constraints 267/0 clauses 26320/0 units 564
0.29/0.31	c vars 6597
0.29/0.32	c objective 2753 + 0
0.29/0.32	c solved in presolving
0.29/0.32	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-2684215-1277514705/watcher-2684215-1277514705 -o /tmp/evaluation-result-2684215-1277514705/solver-2684215-1277514705 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2684215-1277514705.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 25984
/proc/meminfo: memFree=1840040/2059040 swapFree=4139052/4192956
[pid=25984] ppid=25982 vsize=2416 CPUtime=0
/proc/25984/stat : 25984 (pbct) R 25982 25984 25305 0 -1 4202496 296 0 0 0 0 0 0 0 17 0 1 0 127074003 2473984 215 1992294400 134512640 136421960 4289211648 18446744073709551615 135873694 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/25984/statm: 604 215 138 467 0 135 0

[startup+0.039469 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 25984
/proc/meminfo: memFree=1840040/2059040 swapFree=4139052/4192956
[pid=25984] ppid=25982 vsize=2416 CPUtime=0.03
/proc/25984/stat : 25984 (pbct) R 25982 25984 25305 0 -1 4202496 320 0 0 0 3 0 0 0 17 0 1 0 127074003 2473984 239 1992294400 134512640 136421960 4289211648 18446744073709551615 135377209 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/25984/statm: 604 239 146 467 0 135 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 2416

[startup+0.101479 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 25984
/proc/meminfo: memFree=1840040/2059040 swapFree=4139052/4192956
[pid=25984] ppid=25982 vsize=2556 CPUtime=0.09
/proc/25984/stat : 25984 (pbct) R 25982 25984 25305 0 -1 4202496 368 0 0 0 9 0 0 0 17 0 1 0 127074003 2617344 287 1992294400 134512640 136421960 4289211648 18446744073709551615 135160399 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/25984/statm: 639 287 146 467 0 170 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2556

[startup+0.300516 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 25984
/proc/meminfo: memFree=1840040/2059040 swapFree=4139052/4192956
[pid=25984] ppid=25982 vsize=3392 CPUtime=0.29
/proc/25984/stat : 25984 (pbct) R 25982 25984 25305 0 -1 4202496 564 0 0 0 29 0 0 0 17 0 1 0 127074003 3473408 483 1992294400 134512640 136421960 4289211648 18446744073709551615 135825888 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/25984/statm: 848 484 146 467 0 379 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 3392

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

Child status: 0
Real time (s): 0.322494
CPU time (s): 0.32295
CPU user time (s): 0.320951
CPU system time (s): 0.001999
CPU usage (%): 100.141
Max. virtual memory (cumulated for all children) (KiB): 3392

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.320951
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 581
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= 1

runsolver used 0.005999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node007 at 2010-06-26 03:11:45
IDJOB=2684215
IDBENCH=72297
IDSOLVER=1192
FILE ID=node007/2684215-1277514705
PBS_JOBID= 11190641
Free space on /tmp= 62328 MiB

SOLVER NAME= PB/CT 0.1 fixed
BENCH NAME= PB10/normalized-PB10/OPT-BIGINT-LIN/leberre/opb-trendy/misc2010/random/rand.newlist/normalized-randc5b1f2.cudf.trendy.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2684215-1277514705/watcher-2684215-1277514705 -o /tmp/evaluation-result-2684215-1277514705/solver-2684215-1277514705 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2684215-1277514705.opb

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

MD5SUM BENCH= 6aafe628c204287c66baba06106fbd9b
RANDOM SEED=1993631956

node007.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.264
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.52
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.264
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:       1840560 kB
Buffers:         32056 kB
Cached:         102296 kB
SwapCached:       6460 kB
Active:          71428 kB
Inactive:        76252 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1840560 kB
SwapTotal:     4192956 kB
SwapFree:      4139052 kB
Dirty:            2792 kB
Writeback:           0 kB
AnonPages:       11972 kB
Mapped:          11824 kB
Slab:            48968 kB
PageTables:       4116 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182544 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= 62324 MiB
End job on node007 at 2010-06-26 03:11:46