Trace number 357674

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
oree 0.1.2 alphaSAT 0.919859 0.921093

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
prestwich/armies/normalized-army8.9bt.opb
MD5SUM41a419a7ef36b132b62f2564e794a725
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.048991
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables220
Total number of constraints470
Number of constraints which are clauses333
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints135
Minimum length of a constraint1
Maximum length of a constraint64
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 9
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 73
Number of bits of the biggest sum of numbers7
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/0.00	c This is oree version 0.1.2 alpha
0.00/0.00	c (c) roussel@cril.univ-artois.fr
0.00/0.00	c using __gmp_expr<__gmpz_value, __gmpz_value>
0.00/0.00	c parsing...
0.00/0.00	c ...done
0.00/0.00	c #vars=220 #constraints=470 hasObjective=no
0.00/0.00	c res. mode=mod
0.00/0.00	c VSIDS like heuristics
0.00/0.00	c complete search running
0.39/0.46	c restart after 401 decisions
0.59/0.61	c nbDecision=500 #constraints=909
0.89/0.91	c nbDecision=677 #constraints=1075
0.89/0.91	
0.89/0.91	s SATISFIABLE
0.89/0.91	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 -x29
0.89/0.91	v 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 x55 -x56
0.89/0.91	v -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 x76 -x77 -x78 -x79 -x80 -x81 -x82
0.89/0.91	v -x83 -x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 x94 -x95 -x96 -x97 -x98 -x99 x100 -x101 -x102 -x103 -x104 -x105 -x106
0.89/0.91	v -x107 x108 -x109 -x110 -x111 x112 -x113 -x114 -x115 x116 -x117 -x118 -x119 -x120 -x121 -x122 -x123 -x124 -x125 x126 -x127
0.89/0.91	v -x128 -x129 x130 x131 -x132 -x133 x134 -x135 x136 x137 -x138 x139 -x140 x141 -x142 x143 -x144 -x145 x146 x147 -x148 -x149 x150
0.89/0.91	v -x151 x152 -x153 x154 x155 -x156 x157 -x158 x159 -x160 -x161 x162 x163 -x164 -x165 x166 -x167 x168 -x169 -x170 x171 -x172 x173
0.89/0.91	v -x174 -x175 -x176 -x177 x178 -x179 -x180 -x181 x182 -x183 x184 -x185 x186 -x187 -x188 -x189 x190 x191 -x192 x193 -x194 x195
0.89/0.91	v -x196 -x197 -x198 x199 -x200 -x201 -x202 x203 -x204 -x205 -x206 -x207 -x208 x209 -x210 x211 -x212 -x213 x214 -x215 x216 -x217
0.89/0.91	v x218 x219 -x220
0.89/0.91	
0.89/0.91	c user time= 0.91786 s
0.89/0.91	c system time= 0.000999 s
0.89/0.91	c wall clock time=0.917971

Verifier Data (download as text)

OK	0

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node59/watcher-357674-1176834631 -o ROOT/results/node59/solver-357674-1176834631 -C 1800 -W 3600 -M 1800 --output-limit 1,15 oree /tmp/evaluation/357674-1176834631/instance-357674-1176834631.opb mod 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.91 0.95 0.98 3/64 29180
/proc/meminfo: memFree=1841072/2055920 swapFree=4184740/4192956
[pid=29180] ppid=29178 vsize=1468 CPUtime=0
/proc/29180/stat : 29180 (oree) R 29178 29180 28138 0 -1 4194304 183 0 0 0 0 0 0 0 18 0 1 0 131372737 1503232 165 18446744073709551615 134512640 135812674 4294956672 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/29180/statm: 367 166 131 317 0 46 0

[startup+0.0141409 s]
/proc/loadavg: 0.91 0.95 0.98 3/64 29180
/proc/meminfo: memFree=1841072/2055920 swapFree=4184740/4192956
[pid=29180] ppid=29178 vsize=1732 CPUtime=0.01
/proc/29180/stat : 29180 (oree) R 29178 29180 28138 0 -1 4194304 236 0 0 0 1 0 0 0 18 0 1 0 131372737 1773568 218 18446744073709551615 134512640 135812674 4294956672 18446744073709551615 135278973 0 0 4096 17474 0 0 0 17 1 0 0
/proc/29180/statm: 433 218 139 317 0 112 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 1732

[startup+0.101158 s]
/proc/loadavg: 0.91 0.95 0.98 3/64 29180
/proc/meminfo: memFree=1841072/2055920 swapFree=4184740/4192956
[pid=29180] ppid=29178 vsize=1992 CPUtime=0.09
/proc/29180/stat : 29180 (oree) R 29178 29180 28138 0 -1 4194304 304 0 0 0 9 0 0 0 18 0 1 0 131372737 2039808 286 18446744073709551615 134512640 135812674 4294956672 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/29180/statm: 498 286 139 317 0 177 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1992

[startup+0.301195 s]
/proc/loadavg: 0.91 0.95 0.98 3/64 29180
/proc/meminfo: memFree=1841072/2055920 swapFree=4184740/4192956
[pid=29180] ppid=29178 vsize=2516 CPUtime=0.29
/proc/29180/stat : 29180 (oree) R 29178 29180 28138 0 -1 4194304 439 0 0 0 29 0 0 0 19 0 1 0 131372737 2576384 421 18446744073709551615 134512640 135812674 4294956672 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/29180/statm: 629 421 139 317 0 308 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 2516

[startup+0.701271 s]
/proc/loadavg: 0.91 0.95 0.98 3/64 29180
/proc/meminfo: memFree=1841072/2055920 swapFree=4184740/4192956
[pid=29180] ppid=29178 vsize=3436 CPUtime=0.69
/proc/29180/stat : 29180 (oree) R 29178 29180 28138 0 -1 4194304 674 0 0 0 69 0 0 0 22 0 1 0 131372737 3518464 656 18446744073709551615 134512640 135812674 4294956672 18446744073709551615 134710874 0 0 4096 17474 0 0 0 17 1 0 0
/proc/29180/statm: 859 656 139 317 0 538 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 3436

Solver just ended. Dumping a history of the last processes samples

[startup+0.901309 s]
/proc/loadavg: 0.91 0.95 0.98 3/64 29180
/proc/meminfo: memFree=1841072/2055920 swapFree=4184740/4192956
[pid=29180] ppid=29178 vsize=3824 CPUtime=0.89
/proc/29180/stat : 29180 (oree) R 29178 29180 28138 0 -1 4194304 772 0 0 0 89 0 0 0 24 0 1 0 131372737 3915776 754 18446744073709551615 134512640 135812674 4294956672 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/29180/statm: 956 754 139 317 0 635 0
Current children cumulated CPU time (s) 0.89
Current children cumulated vsize (KiB) 3824

Child status: 0
Real time (s): 0.921093
CPU time (s): 0.919859
CPU user time (s): 0.91786
CPU system time (s): 0.001999
CPU usage (%): 99.866
Max. virtual memory (cumulated for all children) (KiB): 3824

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.91786
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 794
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 8
involuntary context switches= 2

runsolver used 0.004999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node59 on Tue Apr 17 18:30:31 UTC 2007

IDJOB= 357674
IDBENCH= 1159
IDSOLVER= 172
FILE ID= node59/357674-1176834631

PBS_JOBID= 4586394

Free space on /tmp= 66343 MiB

SOLVER NAME= oree 0.1.2 alpha
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/prestwich/armies/normalized-army8.9bt.opb
COMMAND LINE= oree /tmp/evaluation/357674-1176834631/instance-357674-1176834631.opb mod           
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node59/watcher-357674-1176834631 -o ROOT/results/node59/solver-357674-1176834631 -C 1800 -W 3600 -M 1800 --output-limit 1,15  oree /tmp/evaluation/357674-1176834631/instance-357674-1176834631.opb mod           

META MD5SUM SOLVER= 4e41df0f0543e325f03c5155f85b9e9b
MD5SUM BENCH=  41a419a7ef36b132b62f2564e794a725

RANDOM SEED= 17585252

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node59.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.268
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.268
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:       1841480 kB
Buffers:         11032 kB
Cached:         143456 kB
SwapCached:       2252 kB
Active:          33156 kB
Inactive:       131472 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1841480 kB
SwapTotal:     4192956 kB
SwapFree:      4184740 kB
Dirty:            1328 kB
Writeback:           0 kB
Mapped:          17104 kB
Slab:            35780 kB
Committed_AS:  1578860 kB
PageTables:       1476 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66343 MiB

End job on node59 on Tue Apr 17 18:30:32 UTC 2007