Trace number 364101

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.16UNSAT 0.303953 0.30594

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/
primes-dimacs-cnf/normalized-ssa6288-047.opb
MD5SUM74304bad8e53580b77abf30e0c0ba7f6
Bench CategoryOPT-SMALLINT (optimisation, small integers)
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.306952
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables20820
Total number of constraints44648
Number of constraints which are clauses44648
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint1
Maximum length of a constraint6
Number of terms in the objective function 20820
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 20820
Number of bits of the sum of numbers in the objective function 15
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 20820
Number of bits of the biggest sum of numbers15
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/364101-1177037084/instance-364101-1177037084.opb
0.00/0.00	c File size is 1543946 bytes.
0.19/0.28	c Highest Coefficient sum: 20820
0.19/0.28	c Parsing was ok!!
0.19/0.28	c Total parsing time: 0.276 s
0.29/0.30	c Var: 20820 Constr: 44648 44648/0/0 Lit: 108243 Watch. Lit: 89292
0.29/0.30	c Obj. Vars: 20820 (100 % of total variables)
0.29/0.30	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.29/0.30	c    0        0      0        0    44648   108243      0      0 0.30
0.29/0.30	s UNSATISFIABLE
0.29/0.30	c Total time: 0.298 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/node45/watcher-364101-1177037084 -o ROOT/results/node45/solver-364101-1177037084 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/364101-1177037084/instance-364101-1177037084.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.91 0.95 0.98 3/77 4551
/proc/meminfo: memFree=1810752/2055920 swapFree=4158476/4192956
[pid=4551] ppid=4549 vsize=13244 CPUtime=0
/proc/4551/stat : 4551 (bsolo3.0.16) R 4549 4551 4286 0 -1 4194304 368 0 0 0 0 0 0 0 18 0 1 0 58554084 13561856 336 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 5162619 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4551/statm: 3311 336 281 324 0 2003 0

[startup+0.0478051 s]
/proc/loadavg: 0.91 0.95 0.98 3/77 4551
/proc/meminfo: memFree=1810752/2055920 swapFree=4158476/4192956
[pid=4551] ppid=4549 vsize=7296 CPUtime=0.04
/proc/4551/stat : 4551 (bsolo3.0.16) R 4549 4551 4286 0 -1 4194304 909 0 0 0 4 0 0 0 18 0 1 0 58554084 7471104 837 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 5162619 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4551/statm: 1824 837 335 324 0 516 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 7296

[startup+0.101786 s]
/proc/loadavg: 0.91 0.95 0.98 3/77 4551
/proc/meminfo: memFree=1810752/2055920 swapFree=4158476/4192956
[pid=4551] ppid=4549 vsize=8532 CPUtime=0.09
/proc/4551/stat : 4551 (bsolo3.0.16) R 4549 4551 4286 0 -1 4194304 1272 0 0 0 9 0 0 0 18 0 1 0 58554084 8736768 1200 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 5162619 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4551/statm: 2133 1200 409 324 0 825 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8532

[startup+0.301806 s]
/proc/loadavg: 0.91 0.95 0.98 3/77 4551
/proc/meminfo: memFree=1810752/2055920 swapFree=4158476/4192956
[pid=4551] ppid=4549 vsize=13956 CPUtime=0.29
/proc/4551/stat : 4551 (bsolo3.0.16) R 4549 4551 4286 0 -1 4194304 3250 0 0 0 28 1 0 0 19 0 1 0 58554084 14290944 2801 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 134562157 0 0 4096 16384 0 0 0 17 1 0 0
/proc/4551/statm: 3489 2801 301 324 0 2558 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 13956

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

Child status: 0
Real time (s): 0.30594
CPU time (s): 0.303953
CPU user time (s): 0.286956
CPU system time (s): 0.016997
CPU usage (%): 99.3505
Max. virtual memory (cumulated for all children) (KiB): 13956

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

runsolver used 0.001999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node45 on Fri Apr 20 02:44:44 UTC 2007

IDJOB= 364101
IDBENCH= 2068
IDSOLVER= 163
FILE ID= node45/364101-1177037084

PBS_JOBID= 4640105

Free space on /tmp= 66442 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-ssa6288-047.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/364101-1177037084/instance-364101-1177037084.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node45/watcher-364101-1177037084 -o ROOT/results/node45/solver-364101-1177037084 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/364101-1177037084/instance-364101-1177037084.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  74304bad8e53580b77abf30e0c0ba7f6

RANDOM SEED= 143679467

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node45.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.218
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.218
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:       1811096 kB
Buffers:         35988 kB
Cached:         142908 kB
SwapCached:      14564 kB
Active:         114708 kB
Inactive:        87928 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1811096 kB
SwapTotal:     4192956 kB
SwapFree:      4158476 kB
Dirty:            6092 kB
Writeback:           0 kB
Mapped:          31864 kB
Slab:            27736 kB
Committed_AS:  1209024 kB
PageTables:       1732 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= 66442 MiB

End job on node45 on Fri Apr 20 02:44:45 UTC 2007