Trace number 39444

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 38.4442 38.4688

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1110974372.opb
MD5SUMc554a2f9e460ec54fba106ea9f102f78
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.012997
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables169
Total number of constraints101
Number of constraints which are clauses30
Number of constraints which are cardinality constraints (but not clauses)70
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint169
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 38
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 1266
Number of bits of the biggest sum of numbers11
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 169 variables and 101 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.015
0.02	c After prepocess the problem consists of 169 variables and 99 constraints.
0.04	c Restart #1 #Var: 169 LB: 0 @ 0.029
0.07	c Restart #2 #Var: 169 LB: 0 @ 0.064
0.12	c Restart #3 #Var: 169 LB: 0 @ 0.115
0.17	c Restart #4 #Var: 169 LB: 0 @ 0.16
0.22	c Restart #5 #Var: 169 LB: 0 @ 0.214
0.31	c Restart #6 #Var: 169 LB: 0 @ 0.302
0.47	c Restart #7 #Var: 169 LB: 0 @ 0.467
0.64	c Restart #8 #Var: 169 LB: 0 @ 0.63
0.80	c Restart #9 #Var: 169 LB: 0 @ 0.796
1.02	c Restart #10 #Var: 169 LB: 0 @ 1.014
1.36	c Restart #11 #Var: 169 LB: 0 @ 1.35
1.69	c Restart #12 #Var: 169 LB: 0 @ 1.687
2.04	c Restart #13 #Var: 169 LB: 0 @ 2.037
2.54	c Restart #14 #Var: 169 LB: 0 @ 2.537
2.91	c Restart #15 #Var: 169 LB: 0 @ 2.906
3.55	c Restart #16 #Var: 169 LB: 0 @ 3.538
4.02	c Restart #17 #Var: 169 LB: 0 @ 4.011
4.63	c Restart #18 #Var: 169 LB: 0 @ 4.624
5.14	c Restart #19 #Var: 169 LB: 0 @ 5.135
5.78	c Restart #20 #Var: 168 LB: 0 @ 5.768
6.66	c Restart #21 #Var: 168 LB: 0 @ 6.656
7.75	c Restart #22 #Var: 168 LB: 0 @ 7.745
8.69	c Restart #23 #Var: 168 LB: 0 @ 8.68
9.64	c Restart #24 #Var: 168 LB: 0 @ 9.635
10.73	c Restart #25 #Var: 165 LB: 0 @ 10.719
11.98	c Restart #26 #Var: 163 LB: 0 @ 11.968
13.55	c Restart #27 #Var: 163 LB: 0 @ 13.531
14.86	c Restart #28 #Var: 162 LB: 0 @ 14.85
16.42	c Restart #29 #Var: 162 LB: 0 @ 16.405
18.09	c Restart #30 #Var: 162 LB: 0 @ 18.073
19.60	c Restart #31 #Var: 162 LB: 0 @ 19.584
21.10	c Restart #32 #Var: 162 LB: 0 @ 21.081
23.14	c Restart #33 #Var: 159 LB: 0 @ 23.118
24.95	c Restart #34 #Var: 156 LB: 0 @ 24.937
26.97	c Restart #35 #Var: 156 LB: 0 @ 26.946
29.62	c Restart #36 #Var: 155 LB: 0 @ 29.604
33.24	c Restart #37 #Var: 152 LB: 0 @ 33.216
37.52	c Restart #38 #Var: 109 LB: 0 @ 37.502
38.45	s UNSATISFIABLE
38.45	c Exit Code: 20
38.45	c Total time: 38.427 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
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node62/watcher-39444-1149208511 -o ROOT/results/node62/solver-39444-1149208511 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node62/39444-1149208511/instance-39444-1149208511.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.85 0.95 0.90 2/64 26913
/proc/meminfo: memFree=1478104/2055920 swapFree=4192956/4192956
[pid=26913] ppid=26911 vsize=2948 CPUtime=0
/proc/26913/stat : 26913 (bsolo) R 26911 26913 26868 0 -1 0 50 0 0 0 0 0 0 0 18 0 1 0 30054648 3018752 34 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 8106788 0 0 4096 0 0 0 0 17 1 0 0
/proc/26913/statm: 806 36 27 55 0 40 0

[startup+10.0025 s]
/proc/loadavg: 0.87 0.95 0.90 2/64 26913
/proc/meminfo: memFree=1442648/2055920 swapFree=4192956/4192956
[pid=26913] ppid=26911 vsize=39948 CPUtime=9.98
/proc/26913/stat : 26913 (bsolo) R 26911 26913 26868 0 -1 0 9256 0 0 0 991 7 0 0 25 0 1 0 30054648 40906752 9171 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134719550 0 0 4096 16384 0 0 0 17 1 0 0
/proc/26913/statm: 9987 9171 296 55 0 8879 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 39948

[startup+20.0087 s]
/proc/loadavg: 0.89 0.96 0.91 2/64 26913
/proc/meminfo: memFree=1416984/2055920 swapFree=4192956/4192956
[pid=26913] ppid=26911 vsize=65708 CPUtime=19.98
/proc/26913/stat : 26913 (bsolo) R 26911 26913 26868 0 -1 0 15670 0 0 0 1986 12 0 0 25 0 1 0 30054648 67284992 15585 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134551577 0 0 4096 16384 0 0 0 17 1 0 0
/proc/26913/statm: 16427 15585 296 55 0 15319 0
Current children cumulated CPU time (s) 19.98
Current children cumulated vsize (Kb) 65708

[startup+30.0148 s]
/proc/loadavg: 0.91 0.96 0.91 2/64 26913
/proc/meminfo: memFree=1392792/2055920 swapFree=4192956/4192956
[pid=26913] ppid=26911 vsize=89876 CPUtime=29.99
/proc/26913/stat : 26913 (bsolo) R 26911 26913 26868 0 -1 0 21704 0 0 0 2980 19 0 0 25 0 1 0 30054648 92033024 21619 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134533905 0 0 4096 16384 0 0 0 17 1 0 0
/proc/26913/statm: 22469 21619 296 55 0 21361 0
Current children cumulated CPU time (s) 29.99
Current children cumulated vsize (Kb) 89876

Child status: 20
Real time (s): 38.4688
CPU time (s): 38.4442
CPU user time (s): 38.1862
CPU system time (s): 0.25796
CPU usage (%): 99.936
Max. virtual memory (cumulated for all children) (Kb): 89876

Launcher Data (download as text)

Begin job on node62 on Fri Jun  2 00:35:11 UTC 2006


FILE ID= 39444-1149208511

PBS_JOBID= 293523

BENCH NAME= ROOT/tmp/node62/39444-1149208511/instance-39444-1149208511.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node62/39444-1149208511/instance-39444-1149208511.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node62/watcher-39444-1149208511 -o ROOT/results/node62/solver-39444-1149208511 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node62/39444-1149208511/instance-39444-1149208511.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  c554a2f9e460ec54fba106ea9f102f78

RANDOM SEED= 677526410


/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.225
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.225
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:       1478312 kB
Buffers:         28168 kB
Cached:         471360 kB
SwapCached:          0 kB
Active:          93516 kB
Inactive:       420472 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1478312 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:             228 kB
Writeback:           0 kB
Mapped:          24896 kB
Slab:            49576 kB
Committed_AS:   115112 kB
PageTables:       1476 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node62 on Fri Jun  2 00:35:50 UTC 2006