Trace number 2683655

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? (problem) 0.145977 0.14591

General information on the benchmark

Name/OPT-SMALLINT-LIN/leberre/opb-paranoid/misc2010/random/
rand.biglist/normalized-rand199fd6.cudf.paranoid.opb
MD5SUMed6439846d599590769e7881fb6d3c5e
Bench CategoryOPT-SMALLINT-LIN (optimisation, small 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.178972
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables6600
Total number of constraints29501
Number of constraints which are clauses29152
Number of constraints which are cardinality constraints (but not clauses)349
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 2426
Biggest coefficient in the objective function 1877
Number of bits for the biggest coefficient in the objective function 11
Sum of the numbers in the objective function 1036102
Number of bits of the sum of numbers in the objective function 20
Biggest number in a constraint 1877
Number of bits of the biggest number in a constraint 11
Biggest sum of numbers in a constraint 1036102
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 

0.00/0.00	c wbo 1.4 beta - 20100517
0.00/0.00	c Parsing opb file format. File HOME/instance-2683655-1277511217.opb.
0.00/0.00	c Instance file HOME/instance-2683655-1277511217.opb
0.00/0.00	c File size is 940072 bytes.
0.09/0.14	c Highest Coefficient sum: 553
0.09/0.14	c ============================[ Problem Statistics ]=============================
0.09/0.14	c |                                                                             |
0.09/0.14	c |  Parsing time:          0.14         s                                      |
0.09/0.14	c |  Number Variables:      6600                                                |
0.09/0.14	c |  Number Clauses:        29152                                               |
0.09/0.14	c |  Number Cardinality:    349                                                 |
0.09/0.14	c |  Number PB Constraints: 0                                                   |

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-2683655-1277511217/watcher-2683655-1277511217 -o /tmp/evaluation-result-2683655-1277511217/solver-2683655-1277511217 -C 1800 -W 2000 -M 1800 wbo1.4b -file-format=opb -time-limit=1800 HOME/instance-2683655-1277511217.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.00 1.00 1.00 3/106 30609
/proc/meminfo: memFree=1815064/2059040 swapFree=4139696/4192956
[pid=30609] ppid=30607 vsize=3956 CPUtime=0
/proc/30609/stat : 30609 (wbo1.4b) R 30607 30609 29624 0 -1 4202496 399 0 0 0 0 0 0 0 15 0 1 0 92409809 4050944 317 1992294400 134512640 135751879 4292400848 18446744073709551615 135010161 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/30609/statm: 989 317 143 303 0 454 0

[startup+0.0602009 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 30609
/proc/meminfo: memFree=1815064/2059040 swapFree=4139696/4192956
[pid=30609] ppid=30607 vsize=4676 CPUtime=0.05
/proc/30609/stat : 30609 (wbo1.4b) R 30607 30609 29624 0 -1 4202496 677 0 0 0 5 0 0 0 17 0 1 0 92409809 4788224 595 1992294400 134512640 135751879 4292400848 18446744073709551615 135188009 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/30609/statm: 1169 595 229 303 0 634 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 4676

[startup+0.101206 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 30609
/proc/meminfo: memFree=1815064/2059040 swapFree=4139696/4192956
[pid=30609] ppid=30607 vsize=5392 CPUtime=0.09
/proc/30609/stat : 30609 (wbo1.4b) R 30607 30609 29624 0 -1 4202496 887 0 0 0 9 0 0 0 17 0 1 0 92409809 5521408 805 1992294400 134512640 135751879 4292400848 18446744073709551615 135204210 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/30609/statm: 1348 805 294 303 0 813 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5392

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

Child status: 0
Real time (s): 0.14591
CPU time (s): 0.145977
CPU user time (s): 0.142978
CPU system time (s): 0.002999
CPU usage (%): 100.046
Max. virtual memory (cumulated for all children) (KiB): 5392

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

runsolver used 0.004999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node049 at 2010-06-26 02:13:38
IDJOB=2683655
IDBENCH=72129
IDSOLVER=1161
FILE ID=node049/2683655-1277511217
PBS_JOBID= 11190642
Free space on /tmp= 62456 MiB

SOLVER NAME= wbo 1.4b
BENCH NAME= PB10/normalized-PB10/OPT-SMALLINT-LIN/leberre/opb-paranoid/misc2010/random/rand.biglist/normalized-rand199fd6.cudf.paranoid.opb
COMMAND LINE= wbo1.4b -file-format=opb -time-limit=TIMEOUT BENCHNAME
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2683655-1277511217/watcher-2683655-1277511217 -o /tmp/evaluation-result-2683655-1277511217/solver-2683655-1277511217 -C 1800 -W 2000 -M 1800  wbo1.4b -file-format=opb -time-limit=1800 HOME/instance-2683655-1277511217.opb

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

MD5SUM BENCH= ed6439846d599590769e7881fb6d3c5e
RANDOM SEED=366402776

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1815716 kB
Buffers:         32596 kB
Cached:         113556 kB
SwapCached:       6424 kB
Active:          95100 kB
Inactive:        64560 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1815716 kB
SwapTotal:     4192956 kB
SwapFree:      4139696 kB
Dirty:            3500 kB
Writeback:           8 kB
AnonPages:       12012 kB
Mapped:          11872 kB
Slab:            61628 kB
PageTables:       4076 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   184644 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264964 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-2683655-1277511217.opb

Free space on /tmp at the end= 62452 MiB
End job on node049 at 2010-06-26 02:13:38