Trace number 350758

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, and are wall clock time (not CPU 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
bsolo 3.0.16Signal 1.21681 1.28036

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/reduced/mps-v2-20-10/plato.asu.edu/
pub/milp/normalized-reduced-mps-v2-20-10-neos20.opb
MD5SUM548627fc5af0dd4663b3515778a6a609
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark-55
Best CPU time to get the best result obtained on this benchmark1800.07
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function -56
Optimality of the best value was proved NO
Number of variables8411
Total number of constraints2456
Number of constraints which are clauses412
Number of constraints which are cardinality constraints (but not clauses)426
Number of constraints which are nor clauses,nor cardinality constraints1618
Minimum length of a constraint2
Maximum length of a constraint270
Number of terms in the objective function 150
Biggest coefficient in the objective function 52429
Number of bits for the biggest coefficient in the objective function 16
Sum of the numbers in the objective function 524390
Number of bits of the sum of numbers in the objective function 20
Biggest number in a constraint 523753
Number of bits of the biggest number in a constraint 19
Biggest sum of numbers in a constraint 524475
Number of bits of the biggest sum of numbers20
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00/0.00	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.00	c Developed by Vasco Manquinho IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/350758-1176547255/instance-350758-1176547255.opb
0.00/0.00	c File size is 351178 bytes.
0.03/0.07	c Highest Coefficient sum: 524475
0.03/0.07	c Parsing was ok!!
0.03/0.07	c Total parsing time: 0.069 s
0.03/0.07	c Var: 8411 Constr: 3209 1468/4/1737 Lit: 50018 Watch. Lit: 20721
0.03/0.07	c Obj. Vars: 150 (1.78338 % of total variables)
1.09/1.19	c Pre-processing Time: 1.195 s
1.09/1.20	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
1.09/1.20	c        0   3310     1833    33389   18    18447   62961      0      0 1.20
1.09/1.20	c Switching off LPR mode.
1.19/1.26	*** glibc detected *** double free or corruption (fasttop): 0x083bc598 ***

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

runsolver version 3.2.2 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node18/watcher-350758-1176547255 -o ROOT/results/node18/solver-350758-1176547255 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350758-1176547255/instance-350758-1176547255.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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.03 1.03 1.00 3/77 25700
/proc/meminfo: memFree=1757504/2055920 swapFree=4168132/4192956
[pid=25700] ppid=25698 vsize=12080 CPUtime=0
/proc/25700/stat : 25700 (bsolo3.0.16) R 25698 25700 24587 0 -1 4194304 370 0 0 0 0 0 0 0 18 0 1 0 102642933 12369920 338 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 8296059 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25700/statm: 3020 338 283 324 0 2003 0

[startup+0.038323 s]
/proc/loadavg: 1.03 1.03 1.00 3/77 25700
/proc/meminfo: memFree=1757504/2055920 swapFree=4168132/4192956
[pid=25700] ppid=25698 vsize=4956 CPUtime=0.03
/proc/25700/stat : 25700 (bsolo3.0.16) R 25698 25700 24587 0 -1 4194304 581 0 0 0 3 0 0 0 18 0 1 0 102642933 5074944 549 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 8296059 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25700/statm: 1239 549 326 324 0 222 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 4956

[startup+0.102329 s]
/proc/loadavg: 1.03 1.03 1.00 3/77 25700
/proc/meminfo: memFree=1757504/2055920 swapFree=4168132/4192956
[pid=25700] ppid=25698 vsize=6644 CPUtime=0.09
/proc/25700/stat : 25700 (bsolo3.0.16) R 25698 25700 24587 0 -1 4194304 1125 0 0 0 9 0 0 0 18 0 1 0 102642933 6803456 1007 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25700/statm: 1661 1007 305 324 0 730 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6644

[startup+0.302347 s]
/proc/loadavg: 1.03 1.03 1.00 3/77 25700
/proc/meminfo: memFree=1757504/2055920 swapFree=4168132/4192956
[pid=25700] ppid=25698 vsize=6644 CPUtime=0.29
/proc/25700/stat : 25700 (bsolo3.0.16) R 25698 25700 24587 0 -1 4194304 1130 0 0 0 29 0 0 0 19 0 1 0 102642933 6803456 1012 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 134551504 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25700/statm: 1661 1012 305 324 0 730 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 6644

[startup+0.701386 s]
/proc/loadavg: 1.03 1.03 1.00 3/77 25700
/proc/meminfo: memFree=1757504/2055920 swapFree=4168132/4192956
[pid=25700] ppid=25698 vsize=6644 CPUtime=0.69
/proc/25700/stat : 25700 (bsolo3.0.16) R 25698 25700 24587 0 -1 4194304 1131 0 0 0 69 0 0 0 23 0 1 0 102642933 6803456 1013 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 134551513 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25700/statm: 1661 1013 305 324 0 730 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 6644

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

[startup+1.10543 s]
/proc/loadavg: 1.03 1.02 1.00 2/78 25701
/proc/meminfo: memFree=1754680/2055920 swapFree=4168132/4192956
[pid=25700] ppid=25698 vsize=6644 CPUtime=1.09
/proc/25700/stat : 25700 (bsolo3.0.16) R 25698 25700 24587 0 -1 4194304 1131 0 0 0 109 0 0 0 25 0 1 0 102642933 6803456 1013 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 134551096 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25700/statm: 1661 1013 305 324 0 730 0
Current children cumulated CPU time (s) 1.09
Current children cumulated vsize (KiB) 6644

[startup+1.20143 s]
/proc/loadavg: 1.03 1.02 1.00 2/78 25701
/proc/meminfo: memFree=1754680/2055920 swapFree=4168132/4192956
[pid=25700] ppid=25698 vsize=6784 CPUtime=1.19
/proc/25700/stat : 25700 (bsolo3.0.16) R 25698 25700 24587 0 -1 4194304 1268 0 0 0 118 1 0 0 25 0 1 0 102642933 6946816 1051 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25700/statm: 1696 1051 309 324 0 765 0
Current children cumulated CPU time (s) 1.19
Current children cumulated vsize (KiB) 6784

Child ended because it received signal 6 (SIGABRT)
Real time (s): 1.28036
CPU time (s): 1.21681
CPU user time (s): 1.18882
CPU system time (s): 0.027995
CPU usage (%): 95.0367
Max. virtual memory (cumulated for all children) (KiB): 6784

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.18882
system time used= 0.027995
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1313
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 15
involuntary context switches= 26

runsolver used 0.002999 second user time and 0.009998 second system time

The end

Launcher Data (download as text)

Begin job on node18 on Sat Apr 14 10:40:56 UTC 2007

IDJOB= 350758
IDBENCH= 1585
IDSOLVER= 163
FILE ID= node18/350758-1176547255

PBS_JOBID= 4556731

Free space on /tmp= 66555 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/reduced/mps-v2-20-10/plato.asu.edu/pub/milp/normalized-reduced-mps-v2-20-10-neos20.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350758-1176547255/instance-350758-1176547255.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node18/watcher-350758-1176547255 -o ROOT/results/node18/solver-350758-1176547255 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350758-1176547255/instance-350758-1176547255.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  548627fc5af0dd4663b3515778a6a609

RANDOM SEED= 179512391

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node18.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.234
cache size	: 2048 KB
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 pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
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.234
cache size	: 2048 KB
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 pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1757912 kB
Buffers:         26460 kB
Cached:         179136 kB
SwapCached:      10644 kB
Active:          51156 kB
Inactive:       195304 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1757912 kB
SwapTotal:     4192956 kB
SwapFree:      4168132 kB
Dirty:            4748 kB
Writeback:           0 kB
Mapped:          40268 kB
Slab:            36984 kB
Committed_AS:  2713940 kB
PageTables:       1780 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66552 MiB

End job on node18 on Sat Apr 14 10:40:57 UTC 2007