Trace number 1726055

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
SATzilla2009_C 2009-03-22SAT 0.009997 0.0104901

General information on the benchmark

Namecrafted/Medium/contest05/jarvisalo/
mod2-rand3bip-sat-220-1.sat05-2173.reshuffled-07.cnf
MD5SUMce96de70272a2ecfcbbf1c8e965c8e57
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.009997
Satisfiable
(Un)Satisfiability was proved
Number of variables220
Number of clauses880
Sum of the clauses size2640
Maximum clause length3
Minimum clause length3
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 3880
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.00/0.01	c SATzilla is building models for class 2
0.00/0.01	c run presolver march_dl2004 for 5 seconds ... 
0.00/0.01	c Bin: Executing march_dl2004
0.00/0.01	c spawning binary file with 5 seconds ...
0.00/0.01	c child exited successfully
0.00/0.01	c march_dl2004 returned code 10.
0.00/0.01	s SATISFIABLE
0.00/0.01	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 0
0.00/0.01	c SATZILLA_TIME=0.000000

Verifier Data 

OK

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1726055-1240708808/watcher-1726055-1240708808 -o /tmp/evaluation-result-1726055-1240708808/solver-1726055-1240708808 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/SATzilla2009_C HOME/instance-1726055-1240708808.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 1800 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.99 0.98 0.99 3/64 24582
/proc/meminfo: memFree=1673920/2055920 swapFree=4181848/4192956
[pid=24582] ppid=24580 vsize=2056 CPUtime=0
/proc/24582/stat : 24582 (SATzilla2009_C) R 24580 24582 24389 0 -1 4194304 128 0 0 0 0 0 0 0 18 0 1 0 98914841 2105344 112 1992294400 134512640 136149437 4294956224 18446744073709551615 135543087 0 0 4096 0 0 0 0 17 0 0 0
/proc/24582/statm: 514 112 96 399 0 111 0
[pid=24583] ppid=24582 vsize=640 CPUtime=0
/proc/24583/stat : 24583 (march_dl2004) R 24582 24582 24389 0 -1 4194304 105 0 0 0 0 0 0 0 18 0 1 0 98914841 655360 97 1992294400 134512640 134996440 4294956192 18446744073709551615 134652876 0 0 8392704 0 0 0 0 17 0 0 0
/proc/24583/statm: 160 97 57 118 0 39 0

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

Child status: 10
Real time (s): 0.0104901
CPU time (s): 0.009997
CPU user time (s): 0.008998
CPU system time (s): 0.000999
CPU usage (%): 95.2995
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.000999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node4 at 2009-04-26 03:20:08
IDJOB=1726055
IDBENCH=24604
IDSOLVER=527
FILE ID=node4/1726055-1240708808
PBS_JOBID= 9186826
Free space on /tmp= 66208 MiB

SOLVER NAME= SATzilla2009_C 2009-03-22
BENCH NAME= SAT07/crafted/Medium/contest05/jarvisalo/mod2-rand3bip-sat-220-1.sat05-2173.reshuffled-07.cnf
COMMAND LINE= HOME/SATzilla2009_C BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1726055-1240708808/watcher-1726055-1240708808 -o /tmp/evaluation-result-1726055-1240708808/solver-1726055-1240708808 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/SATzilla2009_C HOME/instance-1726055-1240708808.cnf

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= ce96de70272a2ecfcbbf1c8e965c8e57
RANDOM SEED=670706362

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

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1674464 kB
Buffers:         42416 kB
Cached:         278136 kB
SwapCached:       5372 kB
Active:         166140 kB
Inactive:       162724 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1674464 kB
SwapTotal:     4192956 kB
SwapFree:      4181848 kB
Dirty:           31464 kB
Writeback:           0 kB
Mapped:          13876 kB
Slab:            38592 kB
Committed_AS:   497880 kB
PageTables:       1468 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= 66176 MiB
End job on node4 at 2009-04-26 03:20:09