Trace number 1732620

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
TNM 2009-03-22SAT 0.911861 0.913293

General information on the benchmark

NameCRAFTED/sgen/sat/
sgen1-sat-200-100.cnf
MD5SUM3eff3d0cb86e42a8fbb844259e0c7beb
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.911861
Satisfiable
(Un)Satisfiability was proved
Number of variables200
Number of clauses480
Sum of the clauses size1200
Maximum clause length5
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 2400
Number of clauses of size 30
Number of clauses of size 40
Number of clauses of size 580
Number of clauses of size over 50

Solver Data 

0.89/0.91	c try 1 flip j 1633511
0.89/0.91	c A solution is found
0.89/0.91	s SATISFIABLE
0.89/0.91	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 
0.89/0.91	v 0 
0.89/0.91	c Done (mycputime is 0.910 seconds)

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-1732620-1240782395/watcher-1732620-1240782395 -o /tmp/evaluation-result-1732620-1240782395/solver-1732620-1240782395 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/TNM HOME/instance-1732620-1240782395.cnf 2042099049 

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.92 0.98 0.99 3/64 21925
/proc/meminfo: memFree=1292400/2055920 swapFree=4192812/4192956
[pid=21925] ppid=21923 vsize=454828 CPUtime=0
/proc/21925/stat : 21925 (TNM) R 21923 21925 21888 0 -1 4194304 132 0 0 0 0 0 0 0 18 0 1 0 106272123 465743872 116 1992294400 134512640 135094415 4294956240 18446744073709551615 134526990 0 0 4096 0 0 0 0 17 1 0 0
/proc/21925/statm: 113707 116 50 142 0 112586 0

[startup+0.010051 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 21925
/proc/meminfo: memFree=1292400/2055920 swapFree=4192812/4192956
[pid=21925] ppid=21923 vsize=454828 CPUtime=0
/proc/21925/stat : 21925 (TNM) R 21923 21925 21888 0 -1 4194304 132 0 0 0 0 0 0 0 18 0 1 0 106272123 465743872 116 1992294400 134512640 135094415 4294956240 18446744073709551615 134528452 0 0 4096 0 0 0 0 17 1 0 0
/proc/21925/statm: 113707 116 50 142 0 112586 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 454828

[startup+0.101061 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 21925
/proc/meminfo: memFree=1292400/2055920 swapFree=4192812/4192956
[pid=21925] ppid=21923 vsize=454828 CPUtime=0.09
/proc/21925/stat : 21925 (TNM) R 21923 21925 21888 0 -1 4194304 132 0 0 0 9 0 0 0 18 0 1 0 106272123 465743872 116 1992294400 134512640 135094415 4294956240 18446744073709551615 134528988 0 0 4096 0 0 0 0 17 1 0 0
/proc/21925/statm: 113707 116 50 142 0 112586 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 454828

[startup+0.301085 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 21925
/proc/meminfo: memFree=1292400/2055920 swapFree=4192812/4192956
[pid=21925] ppid=21923 vsize=454828 CPUtime=0.29
/proc/21925/stat : 21925 (TNM) R 21923 21925 21888 0 -1 4194304 132 0 0 0 29 0 0 0 19 0 1 0 106272123 465743872 116 1992294400 134512640 135094415 4294956240 18446744073709551615 134527896 0 0 4096 0 0 0 0 17 1 0 0
/proc/21925/statm: 113707 116 50 142 0 112586 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 454828

[startup+0.701132 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 21925
/proc/meminfo: memFree=1292400/2055920 swapFree=4192812/4192956
[pid=21925] ppid=21923 vsize=454828 CPUtime=0.69
/proc/21925/stat : 21925 (TNM) R 21923 21925 21888 0 -1 4194304 132 0 0 0 69 0 0 0 23 0 1 0 106272123 465743872 116 1992294400 134512640 135094415 4294956240 18446744073709551615 134527992 0 0 4096 0 0 0 0 17 1 0 0
/proc/21925/statm: 113707 116 50 142 0 112586 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 454828

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

[startup+0.901157 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 21925
/proc/meminfo: memFree=1292400/2055920 swapFree=4192812/4192956
[pid=21925] ppid=21923 vsize=454828 CPUtime=0.89
/proc/21925/stat : 21925 (TNM) R 21923 21925 21888 0 -1 4194304 132 0 0 0 89 0 0 0 24 0 1 0 106272123 465743872 116 1992294400 134512640 135094415 4294956240 18446744073709551615 134526851 0 0 4096 0 0 0 0 17 1 0 0
/proc/21925/statm: 113707 116 50 142 0 112586 0
Current children cumulated CPU time (s) 0.89
Current children cumulated vsize (KiB) 454828

Child status: 10
Real time (s): 0.913293
CPU time (s): 0.911861
CPU user time (s): 0.911861
CPU system time (s): 0
CPU usage (%): 99.8432
Max. virtual memory (cumulated for all children) (KiB): 454828

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

runsolver used 0.001999 second user time and 0.011998 second system time

The end

Launcher Data 

Begin job on node33 at 2009-04-26 23:46:35
IDJOB=1732620
IDBENCH=71124
IDSOLVER=532
FILE ID=node33/1732620-1240782395
PBS_JOBID= 9187299
Free space on /tmp= 66424 MiB

SOLVER NAME= TNM 2009-03-22
BENCH NAME= SAT09/CRAFTED/sgen/sat/sgen1-sat-200-100.cnf
COMMAND LINE= HOME/TNM BENCHNAME RANDOMSEED
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1732620-1240782395/watcher-1732620-1240782395 -o /tmp/evaluation-result-1732620-1240782395/solver-1732620-1240782395 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/TNM HOME/instance-1732620-1240782395.cnf 2042099049

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

MD5SUM BENCH= 3eff3d0cb86e42a8fbb844259e0c7beb
RANDOM SEED=2042099049

node33.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.212
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.212
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:       1292816 kB
Buffers:         73348 kB
Cached:         599036 kB
SwapCached:          0 kB
Active:         289944 kB
Inactive:       396268 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1292816 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            4788 kB
Writeback:           0 kB
Mapped:          23552 kB
Slab:            62948 kB
Committed_AS:   370316 kB
PageTables:       1388 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= 66420 MiB
End job on node33 at 2009-04-26 23:46:36