Trace number 46276

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 NameAnswerCPU timeWall clock time
bsolo 2006/05UNSAT 48.4596 48.4909

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/
submitted-PB06/roussel/normalized-pigeon-cardinality-11-10.opb
MD5SUMe464fa7a3640eb789ffb0025985d1316
Bench CategorySATUNSAT-SMALLINT-LIN (no 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.001999
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables110
Total number of constraints21
Number of constraints which are clauses11
Number of constraints which are cardinality constraints (but not clauses)10
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint10
Maximum length of a constraint11
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 12
Number of bits of the biggest sum of numbers4
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	c Time Limit set via PBTIMEOUT to 1800
0.01	c INFO: OSL Context initialized.
0.02	c Initial problem consists of 110 variables and 21 constraints.
0.02	c Using non-optimization problem switches.
0.02	c No problem reductions applied in OPT. instance.
0.02	c	preprocess terminated. Elapsed time: 0.006
0.02	c After prepocess the problem consists of 110 variables and 21 constraints.
0.02	c Restart #1 #Var: 110 LB: 0 @ 0.013
0.04	c Restart #2 #Var: 110 LB: 0 @ 0.029
0.07	c Restart #3 #Var: 110 LB: 0 @ 0.064
0.12	c Restart #4 #Var: 110 LB: 0 @ 0.115
0.20	c Restart #5 #Var: 110 LB: 0 @ 0.194
0.36	c Restart #6 #Var: 110 LB: 0 @ 0.351
0.58	c Restart #7 #Var: 110 LB: 0 @ 0.574
0.82	c Restart #8 #Var: 110 LB: 0 @ 0.808
1.16	c Restart #9 #Var: 110 LB: 0 @ 1.146
1.71	c Restart #10 #Var: 110 LB: 0 @ 1.701
2.25	c Restart #11 #Var: 110 LB: 0 @ 2.243
3.38	c Restart #12 #Var: 110 LB: 0 @ 3.372
4.41	c Restart #13 #Var: 110 LB: 0 @ 4.401
5.86	c Restart #14 #Var: 110 LB: 0 @ 5.852
7.48	c Restart #15 #Var: 110 LB: 0 @ 7.464
9.19	c Restart #16 #Var: 110 LB: 0 @ 9.178
12.04	c Restart #17 #Var: 110 LB: 0 @ 12.028
14.90	c Restart #18 #Var: 110 LB: 0 @ 14.884
18.85	c Restart #19 #Var: 110 LB: 0 @ 18.829
24.55	c Restart #20 #Var: 109 LB: 0 @ 24.525
32.15	c Restart #21 #Var: 106 LB: 0 @ 32.126
43.97	c Restart #22 #Var: 99 LB: 0 @ 43.945
48.48	s UNSATISFIABLE
48.48	c Exit Code: 20
48.48	c Total time: 48.451 s

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes

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

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node92/watcher-46276-1149806319 -o ROOT/results/node92/solver-46276-1149806319 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node92/46276-1149806319/instance-46276-1149806319.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.92 0.96 0.93 2/67 10143
/proc/meminfo: memFree=1858184/2055892 swapFree=4084924/4096564
[pid=10143] ppid=10141 vsize=4672 CPUtime=0
/proc/10143/stat : 10143 (bsolo) R 10141 10143 10097 0 -1 0 165 0 0 0 0 0 0 0 19 0 1 0 246270761 4784128 146 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 9522497 0 0 4096 0 0 0 0 17 1 0 0
/proc/10143/statm: 1168 148 110 55 0 46 0

[startup+10.0025 s]
/proc/loadavg: 0.93 0.96 0.93 2/67 10143
/proc/meminfo: memFree=1838408/2055892 swapFree=4084924/4096564
[pid=10143] ppid=10141 vsize=24588 CPUtime=9.98
/proc/10143/stat : 10143 (bsolo) R 10141 10143 10097 0 -1 0 5345 0 0 0 992 6 0 0 25 0 1 0 246270761 25178112 5259 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134551582 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10143/statm: 6147 5259 293 55 0 5038 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 24588

[startup+20.0088 s]
/proc/loadavg: 0.94 0.96 0.93 2/67 10143
/proc/meminfo: memFree=1831432/2055892 swapFree=4084924/4096564
[pid=10143] ppid=10141 vsize=31716 CPUtime=19.98
/proc/10143/stat : 10143 (bsolo) R 10141 10143 10097 0 -1 0 7092 0 0 0 1990 8 0 0 25 0 1 0 246270761 32477184 6998 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134548612 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10143/statm: 7929 6998 293 55 0 6820 0
Current children cumulated CPU time (s) 19.98
Current children cumulated vsize (Kb) 31716

[startup+30.0151 s]
/proc/loadavg: 0.95 0.96 0.93 2/67 10143
/proc/meminfo: memFree=1827464/2055892 swapFree=4084924/4096564
[pid=10143] ppid=10141 vsize=35588 CPUtime=29.99
/proc/10143/stat : 10143 (bsolo) R 10141 10143 10097 0 -1 0 8080 0 0 0 2989 10 0 0 25 0 1 0 246270761 36442112 7983 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134548617 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10143/statm: 8897 7983 293 55 0 7788 0
Current children cumulated CPU time (s) 29.99
Current children cumulated vsize (Kb) 35588

[startup+40.0204 s]
/proc/loadavg: 0.96 0.96 0.93 2/67 10143
/proc/meminfo: memFree=1824904/2055892 swapFree=4084924/4096564
[pid=10143] ppid=10141 vsize=38412 CPUtime=39.99
/proc/10143/stat : 10143 (bsolo) R 10141 10143 10097 0 -1 0 8729 0 0 0 3988 11 0 0 25 0 1 0 246270761 39333888 8627 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134548601 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10143/statm: 9603 8627 293 55 0 8494 0
Current children cumulated CPU time (s) 39.99
Current children cumulated vsize (Kb) 38412

Child status: 20
Real time (s): 48.4909
CPU time (s): 48.4596
CPU user time (s): 48.3367
CPU system time (s): 0.122981
CPU usage (%): 99.9356
Max. virtual memory (cumulated for all children) (Kb): 38412
The end

Launcher Data (download as text)

Begin job on node92 on Thu Jun  8 22:38:39 UTC 2006


FILE ID= 46276-1149806319

PBS_JOBID= 379000

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/roussel/normalized-pigeon-cardinality-11-10.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node92/46276-1149806319/instance-46276-1149806319.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node92/watcher-46276-1149806319 -o ROOT/results/node92/solver-46276-1149806319 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node92/46276-1149806319/instance-46276-1149806319.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  e464fa7a3640eb789ffb0025985d1316

RANDOM SEED= 546411795


/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.214
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.19
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.214
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:      2055892 kB
MemFree:       1858392 kB
Buffers:         17724 kB
Cached:         127272 kB
SwapCached:       2904 kB
Active:          36472 kB
Inactive:       117212 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1858392 kB
SwapTotal:     4096564 kB
SwapFree:      4084924 kB
Dirty:             148 kB
Writeback:           0 kB
Mapped:          15268 kB
Slab:            30612 kB
Committed_AS:   482628 kB
PageTables:       1256 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node92 on Thu Jun  8 22:39:27 UTC 2006