Trace number 39467

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 64.3812 64.4288

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1110973670.opb
MD5SUM2d5d56ef88518febfb85606d45805c18
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.385941
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 1248
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.007
0.02	c After prepocess the problem consists of 169 variables and 99 constraints.
0.03	c Restart #1 #Var: 169 LB: 0 @ 0.023
0.07	c Restart #2 #Var: 169 LB: 0 @ 0.055
0.11	c Restart #3 #Var: 169 LB: 0 @ 0.102
0.17	c Restart #4 #Var: 169 LB: 0 @ 0.155
0.23	c Restart #5 #Var: 169 LB: 0 @ 0.216
0.31	c Restart #6 #Var: 169 LB: 0 @ 0.3
0.42	c Restart #7 #Var: 169 LB: 0 @ 0.405
0.56	c Restart #8 #Var: 169 LB: 0 @ 0.546
0.73	c Restart #9 #Var: 169 LB: 0 @ 0.715
0.90	c Restart #10 #Var: 169 LB: 0 @ 0.889
1.13	c Restart #11 #Var: 169 LB: 0 @ 1.119
1.42	c Restart #12 #Var: 169 LB: 0 @ 1.404
1.66	c Restart #13 #Var: 169 LB: 0 @ 1.651
1.94	c Restart #14 #Var: 169 LB: 0 @ 1.925
2.31	c Restart #15 #Var: 169 LB: 0 @ 2.299
2.75	c Restart #16 #Var: 169 LB: 0 @ 2.742
3.25	c Restart #17 #Var: 169 LB: 0 @ 3.237
3.91	c Restart #18 #Var: 169 LB: 0 @ 3.901
4.87	c Restart #19 #Var: 169 LB: 0 @ 4.853
5.64	c Restart #20 #Var: 169 LB: 0 @ 5.625
6.52	c Restart #21 #Var: 169 LB: 0 @ 6.511
7.48	c Restart #22 #Var: 169 LB: 0 @ 7.467
8.70	c Restart #23 #Var: 169 LB: 0 @ 8.691
9.63	c Restart #24 #Var: 169 LB: 0 @ 9.617
10.53	c Restart #25 #Var: 169 LB: 0 @ 10.514
11.59	c Restart #26 #Var: 169 LB: 0 @ 11.573
14.00	c Restart #27 #Var: 169 LB: 0 @ 13.984
15.28	c Restart #28 #Var: 169 LB: 0 @ 15.264
16.58	c Restart #29 #Var: 169 LB: 0 @ 16.56
17.95	c Restart #30 #Var: 169 LB: 0 @ 17.923
19.49	c Restart #31 #Var: 168 LB: 0 @ 19.467
21.91	c Restart #32 #Var: 168 LB: 0 @ 21.888
23.76	c Restart #33 #Var: 168 LB: 0 @ 23.732
25.39	c Restart #34 #Var: 168 LB: 0 @ 25.356
27.95	c Restart #35 #Var: 168 LB: 0 @ 27.921
31.14	c Restart #36 #Var: 168 LB: 0 @ 31.105
33.26	c Restart #37 #Var: 168 LB: 0 @ 33.222
36.42	c Restart #38 #Var: 165 LB: 0 @ 36.387
39.52	c Restart #39 #Var: 165 LB: 0 @ 39.484
44.69	c Restart #40 #Var: 160 LB: 0 @ 44.654
48.20	c Restart #41 #Var: 159 LB: 0 @ 48.156
51.27	c Restart #42 #Var: 159 LB: 0 @ 51.23
56.02	c Restart #43 #Var: 153 LB: 0 @ 55.976
62.23	c Restart #44 #Var: 153 LB: 0 @ 62.186
64.40	s UNSATISFIABLE
64.40	c Exit Code: 20
64.40	c Total time: 64.355 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/node1/watcher-39467-1149210271 -o ROOT/results/node1/solver-39467-1149210271 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node1/39467-1149210271/instance-39467-1149210271.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.85 0.97 0.91 3/64 20399
/proc/meminfo: memFree=1369712/2055920 swapFree=4181380/4192956
[pid=20399] ppid=20397 vsize=4928 CPUtime=0
/proc/20399/stat : 20399 (bsolo) R 20397 20399 20354 0 -1 0 343 0 0 0 0 0 0 0 18 0 1 0 186688679 5046272 307 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 6295255 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20399/statm: 1232 319 216 55 0 124 0

[startup+10.0025 s]
/proc/loadavg: 0.88 0.97 0.91 2/64 20399
/proc/meminfo: memFree=1331768/2055920 swapFree=4181380/4192956
[pid=20399] ppid=20397 vsize=42588 CPUtime=9.98
/proc/20399/stat : 20399 (bsolo) R 20397 20399 20354 0 -1 0 9898 0 0 0 989 9 0 0 25 0 1 0 186688679 43610112 9813 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134542265 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20399/statm: 10647 9813 296 55 0 9539 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 42588

[startup+20.0086 s]
/proc/loadavg: 0.89 0.97 0.91 2/64 20399
/proc/meminfo: memFree=1306040/2055920 swapFree=4181380/4192956
[pid=20399] ppid=20397 vsize=68464 CPUtime=19.98
/proc/20399/stat : 20399 (bsolo) R 20397 20399 20354 0 -1 0 16343 0 0 0 1984 14 0 0 25 0 1 0 186688679 70107136 16258 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20399/statm: 17116 16258 296 55 0 16008 0
Current children cumulated CPU time (s) 19.98
Current children cumulated vsize (Kb) 68464

[startup+30.0158 s]
/proc/loadavg: 0.91 0.97 0.91 2/64 20399
/proc/meminfo: memFree=1284024/2055920 swapFree=4181380/4192956
[pid=20399] ppid=20397 vsize=90428 CPUtime=29.98
/proc/20399/stat : 20399 (bsolo) R 20397 20399 20354 0 -1 0 21848 0 0 0 2980 18 0 0 25 0 1 0 186688679 92598272 21762 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20399/statm: 22607 21762 296 55 0 21499 0
Current children cumulated CPU time (s) 29.98
Current children cumulated vsize (Kb) 90428

[startup+40.0219 s]
/proc/loadavg: 0.92 0.97 0.91 2/64 20399
/proc/meminfo: memFree=1262904/2055920 swapFree=4181380/4192956
[pid=20399] ppid=20397 vsize=111592 CPUtime=39.98
/proc/20399/stat : 20399 (bsolo) R 20397 20399 20354 0 -1 0 27122 0 0 0 3977 21 0 0 25 0 1 0 186688679 114270208 27036 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134533824 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20399/statm: 27898 27036 296 55 0 26790 0
Current children cumulated CPU time (s) 39.98
Current children cumulated vsize (Kb) 111592

[startup+50.0291 s]
/proc/loadavg: 0.93 0.97 0.91 2/64 20399
/proc/meminfo: memFree=1247288/2055920 swapFree=4181380/4192956
[pid=20399] ppid=20397 vsize=127260 CPUtime=49.98
/proc/20399/stat : 20399 (bsolo) R 20397 20399 20354 0 -1 0 31020 0 0 0 4973 25 0 0 25 0 1 0 186688679 130314240 30933 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 6264443 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20399/statm: 31815 30933 296 55 0 30707 0
Current children cumulated CPU time (s) 49.98
Current children cumulated vsize (Kb) 127260

[startup+60.0343 s]
/proc/loadavg: 0.94 0.97 0.91 2/64 20399
/proc/meminfo: memFree=1233720/2055920 swapFree=4181380/4192956
[pid=20399] ppid=20397 vsize=140880 CPUtime=59.99
/proc/20399/stat : 20399 (bsolo) R 20397 20399 20354 0 -1 0 34396 0 0 0 5969 30 0 0 25 0 1 0 186688679 144261120 34309 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134533905 0 0 4096 16384 0 0 0 17 1 0 0
/proc/20399/statm: 35220 34309 296 55 0 34112 0
Current children cumulated CPU time (s) 59.99
Current children cumulated vsize (Kb) 140880

Child status: 20
Real time (s): 64.4288
CPU time (s): 64.3812
CPU user time (s): 64.0453
CPU system time (s): 0.335948
CPU usage (%): 99.9262
Max. virtual memory (cumulated for all children) (Kb): 140880

Launcher Data (download as text)

Begin job on node1 on Fri Jun  2 01:04:31 UTC 2006


FILE ID= 39467-1149210271

PBS_JOBID= 293826

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  2d5d56ef88518febfb85606d45805c18

RANDOM SEED= 592030196


/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.231
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.231
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:       1369984 kB
Buffers:         29064 kB
Cached:         583012 kB
SwapCached:       3596 kB
Active:         222388 kB
Inactive:       398760 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1369984 kB
SwapTotal:     4192956 kB
SwapFree:      4181380 kB
Dirty:             240 kB
Writeback:           0 kB
Mapped:          14948 kB
Slab:            50788 kB
Committed_AS:   176712 kB
PageTables:       1468 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node1 on Fri Jun  2 01:05:36 UTC 2006