Trace number 2680778

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
wbo 1.4b (fixed)UNSAT 0.240963 0.240025

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.272958
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 

0.00/0.00	c wbo 1.4 beta - 20100610
0.00/0.00	c Parsing opb file format. File HOME/instance-2680778-1277453517.opb.
0.00/0.00	c Instance file HOME/instance-2680778-1277453517.opb
0.00/0.00	c File size is 1543946 bytes.
0.19/0.23	c Highest Coefficient sum: 7
0.19/0.23	c ============================[ Problem Statistics ]=============================
0.19/0.23	c |                                                                             |
0.19/0.23	c |  Parsing time:          0.23         s                                      |
0.19/0.23	c |  Number Variables:      20820                                               |
0.19/0.23	c |  Number Clauses:        44648                                               |
0.19/0.23	c |  Number Cardinality:    0                                                   |
0.19/0.23	c |  Number PB Constraints: 0                                                   |
0.19/0.23	c 
0.19/0.23	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-2680778-1277453517/watcher-2680778-1277453517 -o /tmp/evaluation-result-2680778-1277453517/solver-2680778-1277453517 -C 1800 -W 2000 -M 1800 wbo1.4b -file-format=opb -time-limit=1800 HOME/instance-2680778-1277453517.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: 0.99 0.97 0.82 3/106 27228
/proc/meminfo: memFree=1847148/2059040 swapFree=4140228/4192956
[pid=27228] ppid=27226 vsize=4664 CPUtime=0
/proc/27228/stat : 27228 (wbo1.4b) R 27226 27228 27091 0 -1 4202496 408 0 0 0 0 0 0 0 18 0 1 0 86646689 4775936 327 1992294400 134512640 135752675 4293686320 18446744073709551615 134610230 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/27228/statm: 1166 327 134 303 0 484 0

[startup+0.0133129 s]
/proc/loadavg: 0.99 0.97 0.82 3/106 27228
/proc/meminfo: memFree=1847148/2059040 swapFree=4140228/4192956
[pid=27228] ppid=27226 vsize=5096 CPUtime=0.01
/proc/27228/stat : 27228 (wbo1.4b) R 27226 27228 27091 0 -1 4202496 524 0 0 0 1 0 0 0 18 0 1 0 86646689 5218304 443 1992294400 134512640 135752675 4293686320 18446744073709551615 134559885 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/27228/statm: 1274 445 141 303 0 592 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5096

[startup+0.101322 s]
/proc/loadavg: 0.99 0.97 0.82 3/106 27228
/proc/meminfo: memFree=1847148/2059040 swapFree=4140228/4192956
[pid=27228] ppid=27226 vsize=8808 CPUtime=0.09
/proc/27228/stat : 27228 (wbo1.4b) R 27226 27228 27091 0 -1 4202496 1434 0 0 0 9 0 0 0 20 0 1 0 86646689 9019392 1353 1992294400 134512640 135752675 4293686320 18446744073709551615 135225902 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/27228/statm: 2202 1353 278 303 0 1520 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8808

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

[startup+0.201332 s]
/proc/loadavg: 0.99 0.97 0.82 3/106 27228
/proc/meminfo: memFree=1847148/2059040 swapFree=4140228/4192956
[pid=27228] ppid=27226 vsize=9948 CPUtime=0.19
/proc/27228/stat : 27228 (wbo1.4b) R 27226 27228 27091 0 -1 4202496 1854 0 0 0 19 0 0 0 20 0 1 0 86646689 10186752 1773 1992294400 134512640 135752675 4293686320 18446744073709551615 135222005 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/27228/statm: 2487 1774 442 303 0 1805 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 9948

Child status: 0
Real time (s): 0.240025
CPU time (s): 0.240963
CPU user time (s): 0.229965
CPU system time (s): 0.010998
CPU usage (%): 100.391
Max. virtual memory (cumulated for all children) (KiB): 9948

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.229965
system time used= 0.010998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2230
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= 2
involuntary context switches= 3

runsolver used 0.001999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node035 at 2010-06-25 10:11:57
IDJOB=2680778
IDBENCH=2068
IDSOLVER=1190
FILE ID=node035/2680778-1277453517
PBS_JOBID= 11188131
Free space on /tmp= 62436 MiB

SOLVER NAME= wbo 1.4b (fixed)
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-ssa6288-047.opb
COMMAND LINE= wbo1.4b -file-format=opb -time-limit=TIMEOUT BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2680778-1277453517/watcher-2680778-1277453517 -o /tmp/evaluation-result-2680778-1277453517/solver-2680778-1277453517 -C 1800 -W 2000 -M 1800  wbo1.4b -file-format=opb -time-limit=1800 HOME/instance-2680778-1277453517.opb

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

MD5SUM BENCH= 74304bad8e53580b77abf30e0c0ba7f6
RANDOM SEED=1677922319

node035.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.219
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.43
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.219
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.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1847552 kB
Buffers:         55732 kB
Cached:          54752 kB
SwapCached:       5664 kB
Active:          26976 kB
Inactive:        96920 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1847552 kB
SwapTotal:     4192956 kB
SwapFree:      4140228 kB
Dirty:            4124 kB
Writeback:           0 kB
AnonPages:       11944 kB
Mapped:          12028 kB
Slab:            65448 kB
PageTables:       4260 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182092 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= 62432 MiB
End job on node035 at 2010-06-25 10:11:57