Trace number 1778560

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
gNovelty+-T 2009-03-22 (4 threads)SAT 0.1 0.101459

General information on the benchmark

NameRANDOM/MEDIUM/3SAT/SATISFIABLE/440/
unif-k3-r4.25-v440-c1870-S725789261-031.cnf
MD5SUMf67f090e24644066ce5872fbc256498a
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.1
Satisfiable
(Un)Satisfiability was proved
Number of variables440
Number of clauses1870
Sum of the clauses size5610
Maximum clause length3
Minimum clause length3
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 31870
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.00/0.09	c +------------------------------+
0.00/0.09	c | gNovelty+, version 1.0       |
0.00/0.09	c +------------------------------+
0.00/0.09	c gnovelty+ -h for help
0.00/0.09	c 
0.00/0.09	s SATISFIABLE
0.00/0.09	v -1 -2 3 -4 -5 -6 -7 8 9 10 -11 12 13 14 -15 16 -17 18 -19 -20 -21 -22 23 24 -25 26 -27 28 -29 30 31 32 33 34 -35 -36 37 -38 39 40 41 42 43 44 -45 -46 -47 -48 49 50 -51 52 53 -54 -55 -56 -57 58 -59 -60 61 -62 -63 64 -65 -66 67 -68 69 -70 71 72 -73 74 -75 76 -77 78 79 80 -81 -82 83 84 85 86 -87 88 89 -90 -91 92 93 94 95 96 -97 98 99 100 -101 102 -103 104 -105 -106 -107 108 109 -110 111 -112 113 114 -115 -116 -117 118 -119 120 -121 122 -123 -124 -125 -126 127 -128 -129 -130 -131 132 133 -134 -135 -136 137 -138 139 -140 -141 142 143 -144 -145 -146 147 -148 149 -150 -151 -152 153 -154 -155 -156 -157 158 159 160 161 162 -163 -164 165 166 -167 -168 169 170 171 -172 -173 174 175 -176 177 178 179 180 181 182 183 -184 -185 -186 -187 -188 -189 190 -191 -192 -193 194 195 -196 -197 198 199 -200 201 -202 -203 204 -205 -206 207 -208 -209 210 211 212 213 214 215 -216 217 -218 -219 -220 221 222 223 224 -225 -226 -227 228 229 -230 231 -232 -233 234 235 236 -237 238 239 240 241 -242 243 244 -245 246 -247 -248 249 -250 251 -252 -253 254 255 256 -257 258 259 -260 -261 262 -263 264 -265 266 -267 268 269 270 -271 -272 273 -274 -275 -276 277 -278 279 280 281 282 283 284 -285 -286 287 288 -289 -290 -291 -292 293 294 -295 296 -297 298 -299 -300 -301 302 -303 304 305 -306 307 -308 -309 310 -311 -312 -313 -314 -315 316 317 -318 319 320 -321 -322 -323 324 -325 -326 327 -328 329 -330 331 332 333 -334 335 336 337 -338 339 340 -341 342 -343 344 -345 -346 347 -348 349 -350 -351 -352 353 -354 355 356 -357 358 -359 -360 361 -362 -363 -364 -365 -366 367 368 -369 370 -371 -372 373 -374 375 376 377 378 379 380 -381 -382 383 384 -385 386 387 -388 389 -390 -391 392 393 -394 395 -396 -397 -398 399 400 401 402 -403 -404 -405 -406 407 -408 409 -410 411 412 413 414 -415 -416 -417 -418 419 -420 421 -422 423 -424 425 -426 -427 -428 429 -430 431 -432 433 -434 435 -436 437 438 439 -440 0
0.00/0.09	c Done in 0.000000 seconds

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:503) (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w /tmp/evaluation-result-1778560-1243480813/watcher-1778560-1243480813 -o /tmp/evaluation-result-1778560-1243480813/solver-1778560-1243480813 -C 5000 -W 1000 -M 2047 HOME/gnovelty+ HOME/instance-1778560-1243480813.cnf 453654438 4 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 5000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 5030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 1000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 2096128 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 2147328 KiB
Current StackSize limit: 8192 KiB


[startup+0 s]
/proc/loadavg: 1.82 3.27 3.77 2/109 7069
/proc/meminfo: memFree=704908/3368532 swapFree=1959840/1959888
[pid=7069] ppid=7067 vsize=509232 CPUtime=0.01
/proc/7069/stat : 7069 (gnovelty+) R 7067 7069 7955 0 -1 4202496 857 0 0 0 0 1 0 0 25 0 1 0 1112744131 521453568 813 4294967295 134512640 135680988 3214716192 3214715456 134537167 0 0 0 0 0 0 0 17 2 0 0 0
/proc/7069/statm: 127308 813 99 286 0 127020 0

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

Child status: 10
Real time (s): 0.101459
CPU time (s): 0.1
CPU user time (s): 0.04
CPU system time (s): 0.06
CPU usage (%): 98.562
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.04
system time used= 0.06
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 19759
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= 1
involuntary context switches= 3

runsolver used 0 second user time and 0 second system time

The end

Launcher Data 

Begin job on  at 2009-05-28 05:20:13
IDJOB=1778560
IDBENCH=70702
IDSOLVER=617
FILE ID=/1778560-1243480813
PBS_JOBID=
Free space on /tmp= 7987 MiB

SOLVER NAME= gNovelty+-T 2009-03-22 (4 threads)
BENCH NAME= SAT09/RANDOM/MEDIUM/3SAT/SATISFIABLE/440/unif-k3-r4.25-v440-c1870-S725789261-031.cnf
COMMAND LINE= HOME/gnovelty+ BENCHNAME RANDOMSEED MAXNBTHREAD
RUNSOLVER COMMAND LINE= runsolver --timestamp  -w /tmp/evaluation-result-1778560-1243480813/watcher-1778560-1243480813 -o /tmp/evaluation-result-1778560-1243480813/solver-1778560-1243480813 -C 5000 -W 1000 -M 2047  HOME/gnovelty+ HOME/instance-1778560-1243480813.cnf 453654438 4

TIME LIMIT= 5000 seconds
MEMORY LIMIT= 2047 MiB
MAX NB THREAD= 4

MD5SUM BENCH= f67f090e24644066ce5872fbc256498a
RANDOM SEED= 453654438

Linux (none) 2.6.21.5 #6 SMP Wed Jul 4 17:16:38 CEST 2007 i686 GNU/Linux

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.073
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3992.42
clflush size	: 64

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.073
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.12
clflush size	: 64

processor	: 2
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.073
cache size	: 4096 KB
physical id	: 3
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.14
clflush size	: 64

processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.073
cache size	: 4096 KB
physical id	: 3
siblings	: 2
core id		: 1
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.14
clflush size	: 64


/proc/meminfo:
MemTotal:      3368532 kB
MemFree:        707720 kB
Buffers:         41908 kB
Cached:        2437064 kB
SwapCached:          0 kB
Active:        1299736 kB
Inactive:      1198392 kB
HighTotal:     2489216 kB
HighFree:       448164 kB
LowTotal:       879316 kB
LowFree:        259556 kB
SwapTotal:     1959888 kB
SwapFree:      1959840 kB
Dirty:            1368 kB
Writeback:           0 kB
AnonPages:       19184 kB
Mapped:           7772 kB
Slab:           153412 kB
SReclaimable:   138968 kB
SUnreclaim:      14444 kB
PageTables:        656 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   3644152 kB
Committed_AS:   110896 kB
VmallocTotal:   114680 kB
VmallocUsed:      1444 kB
VmallocChunk:   113072 kB

Free space on /tmp at the end= 7987 MiB
End job on  at 2009-05-28 05:20:13