Trace number 296715

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.053991 0.0545839

General information on the benchmark

Namerandom/OnTreshold/7SAT/v45/
unif-k7-r89-v45-c4005-S1155547357-11.SAT.shuffled.cnf
MD5SUMf2ec1271555abc545a13dbf21a5936ee
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.053991
Satisfiable
(Un)Satisfiability was proved
Number of variables45
Number of clauses4005
Sum of the clauses size28035
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 54005

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 384536126 
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 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/node9/watcher-296715-1171826439 -o ROOT/results/node9/solver-296715-1171826439 -C 1200 -M 1800 --output-limit 1,15 /tmp/evaluation/296715-1171826439/saps /tmp/evaluation/296715-1171826439/instance-296715-1171826439.cnf 384536126 

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.95 0.98 0.99 3/77 18410
/proc/meminfo: memFree=1662344/2055920 swapFree=4192812/4192956
[pid=18410] ppid=18408 vsize=5160 CPUtime=0
/proc/18410/stat : 18410 (saps) R 18408 18410 18010 0 -1 4194304 153 0 0 0 0 0 0 0 18 0 1 0 202598502 5283840 138 18446744073709551615 134512640 135167564 4294956624 18446744073709551615 134692457 0 0 4096 0 0 0 0 17 1 0 0
/proc/18410/statm: 1290 138 72 159 0 1129 0

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

Child status: 10
Real time (s): 0.0545839
CPU time (s): 0.053991
CPU user time (s): 0.050992
CPU system time (s): 0.002999
CPU usage (%): 98.9137
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.050992
system time used= 0.002999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 247
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= 1

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node9 on Sun Feb 18 19:20:39 UTC 2007

IDJOB= 296715
IDBENCH= 19944
IDSOLVER= 103
FILE ID= node9/296715-1171826439

PBS_JOBID= 3839367

Free space on /tmp= 66544 MiB

SOLVER NAME= saps 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/random/OnTreshold/7SAT/v45/unif-k7-r89-v45-c4005-S1155547357-11.SAT.shuffled.cnf
COMMAND LINE= /tmp/evaluation/296715-1171826439/saps /tmp/evaluation/296715-1171826439/instance-296715-1171826439.cnf  384536126   
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-296715-1171826439 -o ROOT/results/node9/solver-296715-1171826439 -C 1200 -M 1800 --output-limit 1,15  /tmp/evaluation/296715-1171826439/saps /tmp/evaluation/296715-1171826439/instance-296715-1171826439.cnf  384536126   

META MD5SUM SOLVER= a43f4f4c91c277b32a975fd145ded8eb
MD5SUM BENCH=  f2ec1271555abc545a13dbf21a5936ee

RANDOM SEED= 384536126

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node9.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.263
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.263
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:       1662816 kB
Buffers:         48588 kB
Cached:         220964 kB
SwapCached:          0 kB
Active:         261816 kB
Inactive:        62224 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1662816 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2448 kB
Writeback:           0 kB
Mapped:          73332 kB
Slab:            54728 kB
Committed_AS:  1037420 kB
PageTables:       1688 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= 66544 MiB

End job on node9 on Sun Feb 18 19:20:39 UTC 2007