Trace number 2684209

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.293954 0.293735

General information on the benchmark

Name/OPT-BIGINT-LIN/leberre/opb-trendy/misc2010/
random/rand.newlist/normalized-rand271a0d.cudf.trendy.opb
MD5SUMb5525d34eb6b858bb6f30f172bc29e07
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.293954
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables6388
Total number of constraints26795
Number of constraints which are clauses26522
Number of constraints which are cardinality constraints (but not clauses)273
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 2972
Biggest coefficient in the objective function 3294646272
Number of bits for the biggest coefficient in the objective function 32
Sum of the numbers in the objective function 1818640314791
Number of bits of the sum of numbers in the objective function 41
Biggest number in a constraint 3294646272
Number of bits of the biggest number in a constraint 32
Biggest sum of numbers in a constraint 1818640314791
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.20/0.28	c constraints 273/0 clauses 25862/0 units 506
0.20/0.28	c vars 6388
0.20/0.29	c objective 2651 + 0
0.20/0.29	c solved in presolving
0.20/0.29	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-2684209-1277514699/watcher-2684209-1277514699 -o /tmp/evaluation-result-2684209-1277514699/solver-2684209-1277514699 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2684209-1277514699.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.28 1.06 1.02 3/106 30889
/proc/meminfo: memFree=1828336/2059040 swapFree=4139912/4192956
[pid=30889] ppid=30887 vsize=2416 CPUtime=0
/proc/30889/stat : 30889 (pbct) R 30887 30889 29393 0 -1 4202496 297 0 0 0 0 0 0 0 25 0 1 0 92763935 2473984 217 1992294400 134512640 136421960 4286594784 18446744073709551615 134541311 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/30889/statm: 604 217 140 467 0 135 0

[startup+0.0581941 s]
/proc/loadavg: 1.28 1.06 1.02 3/106 30889
/proc/meminfo: memFree=1828336/2059040 swapFree=4139912/4192956
[pid=30889] ppid=30887 vsize=2552 CPUtime=0.05
/proc/30889/stat : 30889 (pbct) R 30887 30889 29393 0 -1 4202496 335 0 0 0 5 0 0 0 25 0 1 0 92763935 2613248 255 1992294400 134512640 136421960 4286594784 18446744073709551615 135205444 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/30889/statm: 638 255 146 467 0 169 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 2552

[startup+0.101198 s]
/proc/loadavg: 1.28 1.06 1.02 3/106 30889
/proc/meminfo: memFree=1828336/2059040 swapFree=4139912/4192956
[pid=30889] ppid=30887 vsize=2740 CPUtime=0.1
/proc/30889/stat : 30889 (pbct) R 30887 30889 29393 0 -1 4202496 377 0 0 0 10 0 0 0 25 0 1 0 92763935 2805760 297 1992294400 134512640 136421960 4286594784 18446744073709551615 135372664 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/30889/statm: 685 297 146 467 0 216 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 2740

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

[startup+0.201209 s]
/proc/loadavg: 1.28 1.06 1.02 3/106 30889
/proc/meminfo: memFree=1828336/2059040 swapFree=4139912/4192956
[pid=30889] ppid=30887 vsize=3136 CPUtime=0.2
/proc/30889/stat : 30889 (pbct) R 30887 30889 29393 0 -1 4202496 484 0 0 0 20 0 0 0 25 0 1 0 92763935 3211264 404 1992294400 134512640 136421960 4286594784 18446744073709551615 135805316 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/30889/statm: 784 404 146 467 0 315 0
Current children cumulated CPU time (s) 0.2
Current children cumulated vsize (KiB) 3136

Child status: 0
Real time (s): 0.293735
CPU time (s): 0.293954
CPU user time (s): 0.292955
CPU system time (s): 0.000999
CPU usage (%): 100.075
Max. virtual memory (cumulated for all children) (KiB): 3136

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.292955
system time used= 0.000999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 574
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.001999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node083 at 2010-06-26 03:11:42
IDJOB=2684209
IDBENCH=72295
IDSOLVER=1192
FILE ID=node083/2684209-1277514699
PBS_JOBID= 11190591
Free space on /tmp= 62496 MiB

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

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

MD5SUM BENCH= b5525d34eb6b858bb6f30f172bc29e07
RANDOM SEED=2105007606

node083.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.262
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.262
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	: 5999.40
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1828856 kB
Buffers:         26984 kB
Cached:         106596 kB
SwapCached:       5680 kB
Active:          96156 kB
Inactive:        50732 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1828856 kB
SwapTotal:     4192956 kB
SwapFree:      4139912 kB
Dirty:            2960 kB
Writeback:           0 kB
AnonPages:       11720 kB
Mapped:          11956 kB
Slab:            61360 kB
PageTables:       4180 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   183180 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= 62492 MiB
End job on node083 at 2010-06-26 03:11:42