Trace number 39473

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/05SAT 11.6552 11.6823

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1111223696.opb
MD5SUM35d859ff8d89aabca90bcfc52829307f
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.014996
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
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 1220
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.03	c INFO: OSL Context initialized.
0.04	c Initial problem consists of 169 variables and 101 constraints.
0.04	c Using non-optimization problem switches.
0.04	c No problem reductions applied in OPT. instance.
0.04	c	preprocess terminated. Elapsed time: 0.015
0.04	c After prepocess the problem consists of 169 variables and 99 constraints.
0.05	c Restart #1 #Var: 169 LB: 0 @ 0.028
0.08	c Restart #2 #Var: 169 LB: 0 @ 0.058
0.12	c Restart #3 #Var: 169 LB: 0 @ 0.102
0.17	c Restart #4 #Var: 169 LB: 0 @ 0.149
0.24	c Restart #5 #Var: 169 LB: 0 @ 0.217
0.31	c Restart #6 #Var: 169 LB: 0 @ 0.293
0.44	c Restart #7 #Var: 169 LB: 0 @ 0.426
0.59	c Restart #8 #Var: 169 LB: 0 @ 0.565
0.78	c Restart #9 #Var: 169 LB: 0 @ 0.755
0.99	c Restart #10 #Var: 169 LB: 0 @ 0.969
1.21	c Restart #11 #Var: 169 LB: 0 @ 1.188
1.55	c Restart #12 #Var: 169 LB: 0 @ 1.528
1.95	c Restart #13 #Var: 169 LB: 0 @ 1.929
2.42	c Restart #14 #Var: 169 LB: 0 @ 2.394
2.77	c Restart #15 #Var: 169 LB: 0 @ 2.751
3.23	c Restart #16 #Var: 169 LB: 0 @ 3.206
3.67	c Restart #17 #Var: 169 LB: 0 @ 3.648
4.24	c Restart #18 #Var: 169 LB: 0 @ 4.216
5.02	c Restart #19 #Var: 169 LB: 0 @ 5
5.78	c Restart #20 #Var: 169 LB: 0 @ 5.759
6.72	c Restart #21 #Var: 169 LB: 0 @ 6.691
7.75	c Restart #22 #Var: 169 LB: 0 @ 7.731
9.02	c Restart #23 #Var: 169 LB: 0 @ 9.001
9.89	c Restart #24 #Var: 169 LB: 0 @ 9.865
11.14	c Restart #25 #Var: 169 LB: 0 @ 11.112
11.67	c Sol. found (all assignments made)...
11.67	o 0
11.67	c NEW SOLUTION FOUND: 0 @ 11.644
11.67	s SATISFIABLE
11.67	c Cost: 0
11.67	v -x1 x2 -x3 -x4 -x5 -x6 -x7 -x8 -x9 -x10 -x11 -x12 -x13 -x14 -x15 -x16 -x17 -x18 -x19 -x20 -x21 x22 -x23 -x24 -x25 -x26 -x27 -x28
11.67	v -x29 -x30 x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 x47 -x48 -x49 -x50 -x51 -x52 -x53 -x54
11.67	v -x55 x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 x76 -x77 -x78 -x79 -x80
11.67	v -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 x91 -x92 -x93 -x94 -x95 -x96 x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 x105
11.67	v -x106 -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 x120 -x121 -x122 -x123 -x124 -x125 -x126
11.67	v -x127 -x128 -x129 -x130 -x131 -x132 -x133 -x134 -x135 -x136 x137 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x147
11.67	v -x148 -x149 -x150 -x151 -x152 -x153 -x154 x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 x166 -x167 -x168
11.67	v -x169
11.67	c Exit Code: 10
11.67	c Total time: 11.645 s

Verifier Data (download as text)

OK	0

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/node39/watcher-39473-1149210425 -o ROOT/results/node39/solver-39473-1149210425 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node39/39473-1149210425/instance-39473-1149210425.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.77 0.91 0.90 2/64 30435
/proc/meminfo: memFree=1351624/2055920 swapFree=4180888/4192956
[pid=30435] ppid=30433 vsize=4928 CPUtime=0
/proc/30435/stat : 30435 (bsolo) R 30433 30435 30390 0 -1 0 319 0 0 0 0 0 0 0 19 0 1 0 186708769 5046272 288 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4159295081 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30435/statm: 1232 295 198 55 0 124 0

[startup+10.0022 s]
/proc/loadavg: 0.81 0.91 0.90 2/64 30435
/proc/meminfo: memFree=1312648/2055920 swapFree=4180888/4192956
[pid=30435] ppid=30433 vsize=43368 CPUtime=9.97
/proc/30435/stat : 30435 (bsolo) R 30433 30435 30390 0 -1 0 10098 0 0 0 987 10 0 0 25 0 1 0 186708769 44408832 10013 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 134548456 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30435/statm: 10842 10013 296 55 0 9734 0
Current children cumulated CPU time (s) 9.97
Current children cumulated vsize (Kb) 43368

Child status: 10
Real time (s): 11.6823
CPU time (s): 11.6552
CPU user time (s): 11.5302
CPU system time (s): 0.124981
CPU usage (%): 99.7679
Max. virtual memory (cumulated for all children) (Kb): 43368

Launcher Data (download as text)

Begin job on node39 on Fri Jun  2 01:07:05 UTC 2006


FILE ID= 39473-1149210425

PBS_JOBID= 293903

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

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  35d859ff8d89aabca90bcfc52829307f

RANDOM SEED= 870352150


/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.213
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	: 5931.00
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.213
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:       1351832 kB
Buffers:         43788 kB
Cached:         586260 kB
SwapCached:       4052 kB
Active:         214940 kB
Inactive:       424096 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1351832 kB
SwapTotal:     4192956 kB
SwapFree:      4180888 kB
Dirty:             288 kB
Writeback:           0 kB
Mapped:          14820 kB
Slab:            51104 kB
Committed_AS:   178096 kB
PageTables:       1428 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node39 on Fri Jun  2 01:07:16 UTC 2006