Trace number 39428

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 61.3757 67.9594

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1110966688.opb
MD5SUM8e7a33f6f23050442c6613e25c3d2ac1
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.090985
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 1237
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)

6.53	c Time Limit set via PBTIMEOUT to 1800
6.56	c INFO: OSL Context initialized.
6.57	c Initial problem consists of 169 variables and 101 constraints.
6.57	c Using non-optimization problem switches.
6.57	c No problem reductions applied in OPT. instance.
6.57	c	preprocess terminated. Elapsed time: 0.01
6.57	c After prepocess the problem consists of 169 variables and 99 constraints.
6.58	c Restart #1 #Var: 169 LB: 0 @ 0.024
6.61	c Restart #2 #Var: 169 LB: 0 @ 0.055
6.66	c Restart #3 #Var: 169 LB: 0 @ 0.107
6.72	c Restart #4 #Var: 169 LB: 0 @ 0.16
6.77	c Restart #5 #Var: 169 LB: 0 @ 0.217
6.86	c Restart #6 #Var: 169 LB: 0 @ 0.305
6.96	c Restart #7 #Var: 169 LB: 0 @ 0.406
7.12	c Restart #8 #Var: 169 LB: 0 @ 0.566
7.28	c Restart #9 #Var: 169 LB: 0 @ 0.719
7.46	c Restart #10 #Var: 169 LB: 0 @ 0.903
7.74	c Restart #11 #Var: 169 LB: 0 @ 1.182
7.98	c Restart #12 #Var: 169 LB: 0 @ 1.427
8.30	c Restart #13 #Var: 169 LB: 0 @ 1.741
8.71	c Restart #14 #Var: 169 LB: 0 @ 2.155
9.00	c Restart #15 #Var: 169 LB: 0 @ 2.446
9.48	c Restart #16 #Var: 169 LB: 0 @ 2.923
9.85	c Restart #17 #Var: 169 LB: 0 @ 3.296
10.33	c Restart #18 #Var: 169 LB: 0 @ 3.766
10.92	c Restart #19 #Var: 169 LB: 0 @ 4.363
11.44	c Restart #20 #Var: 169 LB: 0 @ 4.878
12.19	c Restart #21 #Var: 169 LB: 0 @ 5.631
13.03	c Restart #22 #Var: 169 LB: 0 @ 6.474
13.99	c Restart #23 #Var: 169 LB: 0 @ 7.429
14.96	c Restart #24 #Var: 169 LB: 0 @ 8.395
16.28	c Restart #25 #Var: 169 LB: 0 @ 9.716
17.27	c Restart #26 #Var: 169 LB: 0 @ 10.703
19.07	c Restart #27 #Var: 169 LB: 0 @ 12.507
20.14	c Restart #28 #Var: 169 LB: 0 @ 13.571
22.28	c Restart #29 #Var: 169 LB: 0 @ 15.712
23.29	c Restart #30 #Var: 168 LB: 0 @ 16.726
24.85	c Restart #31 #Var: 168 LB: 0 @ 18.284
26.91	c Restart #32 #Var: 168 LB: 0 @ 20.345
29.50	c Restart #33 #Var: 168 LB: 0 @ 22.931
31.53	c Restart #34 #Var: 168 LB: 0 @ 24.961
33.76	c Restart #35 #Var: 168 LB: 0 @ 27.194
36.32	c Restart #36 #Var: 168 LB: 0 @ 29.755
38.78	c Restart #37 #Var: 168 LB: 0 @ 32.208
43.42	c Restart #38 #Var: 168 LB: 0 @ 36.845
46.71	c Restart #39 #Var: 165 LB: 0 @ 40.133
50.73	c Restart #40 #Var: 165 LB: 0 @ 44.16
53.52	c Restart #41 #Var: 165 LB: 0 @ 46.947
57.67	c Restart #42 #Var: 159 LB: 0 @ 51.09
61.85	c Restart #43 #Var: 159 LB: 0 @ 55.269
67.22	c Restart #44 #Var: 129 LB: 0 @ 60.639
67.93	s UNSATISFIABLE
67.93	c Exit Code: 20
67.93	c Total time: 61.351 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/node83/watcher-39428-1149206788 -o ROOT/results/node83/solver-39428-1149206788 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node83/39428-1149206788/instance-39428-1149206788.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.76 0.93 0.87 3/67 18389
/proc/meminfo: memFree=1635424/2055888 swapFree=4085416/4096564
[pid=18389] ppid=18387 vsize=2900 CPUtime=0
/proc/18389/stat : 18389 (bsolo) D 18387 18389 18344 0 -1 0 38 0 0 0 0 0 0 0 18 0 1 0 186318150 2969600 24 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 11740311 0 0 4096 0 18446744071563481621 0 0 17 1 0 0
/proc/18389/statm: 725 24 18 55 0 19 0

[startup+10.002 s]
/proc/loadavg: 0.87 0.95 0.88 2/67 18389
/proc/meminfo: memFree=1613216/2055888 swapFree=4085416/4096564
[pid=18389] ppid=18387 vsize=24244 CPUtime=3.44
/proc/18389/stat : 18389 (bsolo) R 18387 18389 18344 0 -1 0 5288 0 10 0 341 3 0 0 25 0 1 0 186318150 24825856 5214 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134718240 0 0 4096 16384 0 0 0 17 1 0 0
/proc/18389/statm: 6061 5214 293 55 0 4952 0
Current children cumulated CPU time (s) 3.44
Current children cumulated vsize (Kb) 24244

[startup+20.0079 s]
/proc/loadavg: 0.89 0.95 0.88 2/67 18389
/proc/meminfo: memFree=1581728/2055888 swapFree=4085416/4096564
[pid=18389] ppid=18387 vsize=55656 CPUtime=13.43
/proc/18389/stat : 18389 (bsolo) R 18387 18389 18344 0 -1 0 13157 0 10 0 1333 10 0 0 25 0 1 0 186318150 56991744 13083 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134718305 0 0 4096 16384 0 0 0 17 1 0 0
/proc/18389/statm: 13914 13083 293 55 0 12805 0
Current children cumulated CPU time (s) 13.43
Current children cumulated vsize (Kb) 55656

[startup+30.0138 s]
/proc/loadavg: 0.91 0.95 0.88 2/67 18389
/proc/meminfo: memFree=1559456/2055888 swapFree=4085416/4096564
[pid=18389] ppid=18387 vsize=77992 CPUtime=23.44
/proc/18389/stat : 18389 (bsolo) R 18387 18389 18344 0 -1 0 18724 0 10 0 2328 16 0 0 25 0 1 0 186318150 79863808 18650 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/18389/statm: 19498 18650 293 55 0 18389 0
Current children cumulated CPU time (s) 23.44
Current children cumulated vsize (Kb) 77992

[startup+40.0197 s]
/proc/loadavg: 0.92 0.95 0.88 2/67 18389
/proc/meminfo: memFree=1539808/2055888 swapFree=4085416/4096564
[pid=18389] ppid=18387 vsize=97704 CPUtime=33.44
/proc/18389/stat : 18389 (bsolo) R 18387 18389 18344 0 -1 0 23631 0 10 0 3323 21 0 0 25 0 1 0 186318150 100048896 23557 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134548453 0 0 4096 16384 0 0 0 17 1 0 0
/proc/18389/statm: 24426 23557 293 55 0 23317 0
Current children cumulated CPU time (s) 33.44
Current children cumulated vsize (Kb) 97704

[startup+50.0256 s]
/proc/loadavg: 0.93 0.95 0.88 2/67 18389
/proc/meminfo: memFree=1525088/2055888 swapFree=4085416/4096564
[pid=18389] ppid=18387 vsize=112492 CPUtime=43.44
/proc/18389/stat : 18389 (bsolo) R 18387 18389 18344 0 -1 0 27316 0 10 0 4319 25 0 0 25 0 1 0 186318150 115191808 27242 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/18389/statm: 28123 27242 293 55 0 27014 0
Current children cumulated CPU time (s) 43.44
Current children cumulated vsize (Kb) 112492

[startup+60.0315 s]
/proc/loadavg: 0.94 0.95 0.88 2/67 18389
/proc/meminfo: memFree=1508256/2055888 swapFree=4085416/4096564
[pid=18389] ppid=18387 vsize=129428 CPUtime=53.44
/proc/18389/stat : 18389 (bsolo) R 18387 18389 18344 0 -1 0 31521 0 10 0 5314 30 0 0 25 0 1 0 186318150 132534272 31447 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134529235 0 0 4096 16384 0 0 0 17 1 0 0
/proc/18389/statm: 32357 31447 293 55 0 31248 0
Current children cumulated CPU time (s) 53.44
Current children cumulated vsize (Kb) 129428

Child status: 20
Real time (s): 67.9594
CPU time (s): 61.3757
CPU user time (s): 61.0147
CPU system time (s): 0.360945
CPU usage (%): 90.3123
Max. virtual memory (cumulated for all children) (Kb): 129428

Launcher Data (download as text)

Begin job on node83 on Fri Jun  2 00:06:28 UTC 2006


FILE ID= 39428-1149206788

PBS_JOBID= 293310

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  8e7a33f6f23050442c6613e25c3d2ac1

RANDOM SEED= 35375409


/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.265
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.16
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.265
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.44
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1635696 kB
Buffers:         27284 kB
Cached:         319284 kB
SwapCached:       2884 kB
Active:          85764 kB
Inactive:       270088 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1635696 kB
SwapTotal:     4096564 kB
SwapFree:      4085416 kB
Dirty:             252 kB
Writeback:           0 kB
Mapped:          16884 kB
Slab:            51012 kB
Committed_AS:   198712 kB
PageTables:       1284 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node83 on Fri Jun  2 00:07:36 UTC 2006