Trace number 295936

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
saps 2007-02-08SAT 0.05399 0.0561049

General information on the benchmark

Namerandom/OnTreshold/7SAT/v70/
unif-k7-r89-v70-c6230-S1635684145-01.SAT.shuffled.cnf
MD5SUM3ad5550996030deea0dfd0153b93e1d4
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.051991
Satisfiable
(Un)Satisfiability was proved
Number of variables70
Number of clauses6230
Sum of the clauses size43610
Maximum clause length7
Minimum clause length7
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 30
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 56230

Solver Data (download as text)

0.00/0.05	c 
0.00/0.05	c UBCSAT version 1.1.0rr
0.00/0.05	c 
0.00/0.05	c http://www.satlib.org/ubcsat
0.00/0.05	c 
0.00/0.05	c ubcsat -h for help
0.00/0.05	c 
0.00/0.05	c  -runs 1 
0.00/0.05	c  -cutoff 4294967295 
0.00/0.05	c  -timeout 0.000000 
0.00/0.05	c  -gtimeout 0.000000 
0.00/0.05	c  -noimprove 0 
0.00/0.05	c  -target 0 
0.00/0.05	c  -wtarget 0.000000 
0.00/0.05	c  -seed 449575283 
0.00/0.05	c  -solve 0 
0.00/0.05	c  -find,-numsol 0 
0.00/0.05	c  -findunique 0 
0.00/0.05	c  -srestart 0 
0.00/0.05	c  -prestart 0.000000 
0.00/0.05	c  -drestart 0 
0.00/0.05	c 
0.00/0.05	c  -alpha 1.300000 
0.00/0.05	c  -rho 0.800000 
0.00/0.05	c  -ps 0.050000 
0.00/0.05	c  -wp 0.010000 
0.00/0.05	c  -sapsthresh -0.100000 
0.00/0.05	c 
0.00/0.05	s SATISFIABLE
0.00/0.05	v  -1 2 3 -4 5 6 -7 8 -9 10
0.00/0.05	v  11 12 -13 14 15 16 -17 -18 19 -20
0.00/0.05	v  21 -22 23 -24 -25 -26 27 28 -29 -30
0.00/0.05	v  31 32 33 -34 -35 36 -37 -38 -39 40
0.00/0.05	v  41 -42 -43 44 45 46 -47 -48 49 -50
0.00/0.05	v  51 52 -53 -54 -55 -56 57 58 -59 60
0.00/0.05	v  -61 -62 63 64 65 66 -67 -68 -69 70
0.00/0.05	v  0

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node7/watcher-295936-1171814811 -o ROOT/results/node7/solver-295936-1171814811 -C 1200 -M 1800 --output-limit 1,15 /tmp/evaluation/295936-1171814811/saps /tmp/evaluation/295936-1171814811/instance-295936-1171814811.cnf 449575283 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 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/77 19314
/proc/meminfo: memFree=1694608/2055920 swapFree=4142368/4192956
[pid=19314] ppid=19312 vsize=5160 CPUtime=0
/proc/19314/stat : 19314 (saps) R 19312 19314 18865 0 -1 4194304 153 0 0 0 0 0 0 0 18 0 1 0 201435791 5283840 138 18446744073709551615 134512640 135167564 4294956624 18446744073709551615 134692457 0 0 4096 0 0 0 0 17 1 0 0
/proc/19314/statm: 1290 138 73 159 0 1129 0

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

Child status: 10
Real time (s): 0.0561049
CPU time (s): 0.05399
CPU user time (s): 0.052991
CPU system time (s): 0.000999
CPU usage (%): 96.2304
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.052991
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= 293
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= 0

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node7 on Sun Feb 18 16:06:51 UTC 2007

IDJOB= 295936
IDBENCH= 19925
IDSOLVER= 103
FILE ID= node7/295936-1171814811

PBS_JOBID= 3839344

Free space on /tmp= 66546 MiB

SOLVER NAME= saps 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/random/OnTreshold/7SAT/v70/unif-k7-r89-v70-c6230-S1635684145-01.SAT.shuffled.cnf
COMMAND LINE= /tmp/evaluation/295936-1171814811/saps /tmp/evaluation/295936-1171814811/instance-295936-1171814811.cnf  449575283   
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node7/watcher-295936-1171814811 -o ROOT/results/node7/solver-295936-1171814811 -C 1200 -M 1800 --output-limit 1,15  /tmp/evaluation/295936-1171814811/saps /tmp/evaluation/295936-1171814811/instance-295936-1171814811.cnf  449575283   

META MD5SUM SOLVER= a43f4f4c91c277b32a975fd145ded8eb
MD5SUM BENCH=  3ad5550996030deea0dfd0153b93e1d4

RANDOM SEED= 449575283

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node7.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.232
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.232
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:       1695080 kB
Buffers:         48488 kB
Cached:         215308 kB
SwapCached:      16024 kB
Active:         208948 kB
Inactive:        84968 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1695080 kB
SwapTotal:     4192956 kB
SwapFree:      4142368 kB
Dirty:            2392 kB
Writeback:           0 kB
Mapped:          29772 kB
Slab:            52472 kB
Committed_AS:   725204 kB
PageTables:       1764 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= 66546 MiB

End job on node7 on Sun Feb 18 16:06:51 UTC 2007