Trace number 354205

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 0.499923 0.502956

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/
lp/data/normalized-mps-v2-20-10-recipe.opb
MD5SUM19c812fe81842f9b63508fc356bab039
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark-127156975
Best CPU time to get the best result obtained on this benchmark1800.7
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function -130330680
Optimality of the best value was proved NO
Number of variables3671
Total number of constraints159
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints159
Minimum length of a constraint10
Maximum length of a constraint420
Number of terms in the objective function 1055
Biggest coefficient in the objective function 65536000
Number of bits for the biggest coefficient in the objective function 26
Sum of the numbers in the objective function 584330055
Number of bits of the sum of numbers in the objective function 30
Biggest number in a constraint 5681631310381056
Number of bits of the biggest number in a constraint 53
Biggest sum of numbers in a constraint 98271137637301167
Number of bits of the biggest sum of numbers57
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/354205-1176699204/instance-354205-1176699204.opb
0.00/0.00	c File size is 266449 bytes.
0.00/0.00	c Coefficients are big enough for not using lower bounding.
0.00/0.00	c Coefficients are big enough for not using lower bounding.
0.00/0.00	c Coefficients are big enough for not using lower bounding.
0.00/0.00	c Coefficients are big enough for not using lower bounding.
0.00/0.00	c Coefficients are big enough for not using lower bounding.
0.00/0.00	c Coefficients are big enough for not using lower bounding.
0.00/0.00	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.01	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.02	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.03	c Coefficients are big enough for not using lower bounding.
0.00/0.04	c Coefficients are big enough for not using lower bounding.
0.00/0.04	c Coefficients are big enough for not using lower bounding.
0.00/0.04	c Highest Coefficient sum: 9.82711e+16
0.00/0.04	c Parsing was ok!!
0.00/0.04	c Total parsing time: 0.037 s
0.00/0.04	c Var: 3671 Constr: 223 4/0/219 Lit: 26041 Watch. Lit: 6328
0.00/0.04	c Obj. Vars: 1055 (28.7388 % of total variables)
0.39/0.44	c Pre-processing Time: 0.445 s

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/node76/watcher-354205-1176699204 -o ROOT/results/node76/solver-354205-1176699204 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354205-1176699204/instance-354205-1176699204.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: 0.92 0.98 0.99 3/69 836
/proc/meminfo: memFree=1827632/2055888 swapFree=4087308/4096564
[pid=836] ppid=834 vsize=12004 CPUtime=0
/proc/836/stat : 836 (bsolo3.0.16) R 834 836 32585 0 -1 4194304 367 0 0 0 0 0 0 0 18 0 1 0 117834987 12292096 336 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 5253163 0 0 4096 16384 0 0 0 17 1 0 0
/proc/836/statm: 3001 337 280 324 0 2003 0

[startup+0.0530429 s]
/proc/loadavg: 0.92 0.98 0.99 3/69 836
/proc/meminfo: memFree=1827632/2055888 swapFree=4087308/4096564
[pid=836] ppid=834 vsize=5344 CPUtime=0.04
/proc/836/stat : 836 (bsolo3.0.16) R 834 836 32585 0 -1 4194304 778 0 0 0 4 0 0 0 18 0 1 0 117834987 5472256 681 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/836/statm: 1336 681 303 324 0 404 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5344

[startup+0.102052 s]
/proc/loadavg: 0.92 0.98 0.99 3/69 836
/proc/meminfo: memFree=1827632/2055888 swapFree=4087308/4096564
[pid=836] ppid=834 vsize=5344 CPUtime=0.09
/proc/836/stat : 836 (bsolo3.0.16) R 834 836 32585 0 -1 4194304 789 0 0 0 9 0 0 0 18 0 1 0 117834987 5472256 692 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/836/statm: 1336 692 303 324 0 404 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5344

[startup+0.30109 s]
/proc/loadavg: 0.92 0.98 0.99 3/69 836
/proc/meminfo: memFree=1827632/2055888 swapFree=4087308/4096564
[pid=836] ppid=834 vsize=5664 CPUtime=0.29
/proc/836/stat : 836 (bsolo3.0.16) R 834 836 32585 0 -1 4194304 914 0 0 0 29 0 0 0 19 0 1 0 117834987 5799936 765 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/836/statm: 1416 765 305 324 0 484 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 5664

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

[startup+0.50213 s]
/proc/loadavg: 0.92 0.98 0.99 3/69 836
/proc/meminfo: memFree=1827632/2055888 swapFree=4087308/4096564
[pid=836] ppid=834 vsize=0 CPUtime=0.49
/proc/836/stat : 836 (bsolo3.0.16) D 834 836 32585 0 -1 4195844 959 0 0 0 48 1 0 0 22 0 1 0 117834987 0 0 18446744073709551615 0 0 0 0 0 0 2147483391 4096 16384 18446744072099941670 0 0 17 1 0 0
/proc/836/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 0

Child ended because it received signal 11 (SIGSEGV)
Real time (s): 0.502956
CPU time (s): 0.499923
CPU user time (s): 0.487925
CPU system time (s): 0.011998
CPU usage (%): 99.397
Max. virtual memory (cumulated for all children) (KiB): 5664

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.487925
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 959
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= 12
involuntary context switches= 1

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node76 on Mon Apr 16 04:53:24 UTC 2007

IDJOB= 354205
IDBENCH= 2395
IDSOLVER= 163
FILE ID= node76/354205-1176699204

PBS_JOBID= 4560024

Free space on /tmp= 66637 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/lp/data/normalized-mps-v2-20-10-recipe.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354205-1176699204/instance-354205-1176699204.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-354205-1176699204 -o ROOT/results/node76/solver-354205-1176699204 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354205-1176699204/instance-354205-1176699204.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  19c812fe81842f9b63508fc356bab039

RANDOM SEED= 767247189

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node76.alineos.net 2.6.9-34.ELsmp #1 SMP Thu Mar 9 06:23:23 GMT 2006 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.277
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	: 6006.17
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.277
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1828040 kB
Buffers:         72868 kB
Cached:          96844 kB
SwapCached:       2600 kB
Active:          55940 kB
Inactive:       126068 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1828040 kB
SwapTotal:     4096564 kB
SwapFree:      4087308 kB
Dirty:            4652 kB
Writeback:           0 kB
Mapped:          16988 kB
Slab:            32272 kB
Committed_AS:  5154204 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66635 MiB

End job on node76 on Mon Apr 16 04:53:25 UTC 2007