Trace number 370065

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
TTS 4.0UNSAT 0.59091 0.59083

General information on the benchmark

Namecrafted/Medium/contest05/pebbling/
unsat-pbl-00090.sat05-1326.reshuffled-07.cnf
MD5SUMfc73c241ff6e8e1a49a6ff2500eb7905
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.265959
Satisfiable
(Un)Satisfiability was proved
Number of variables322
Number of clauses9322
Sum of the clauses size72335
Maximum clause length11
Minimum clause length1
Number of clauses of size 11
Number of clauses of size 211
Number of clauses of size 379
Number of clauses of size 4136
Number of clauses of size 5421
Number of clauses of size over 58674

Solver Data (download as text)

0.50/0.58	c Command: /tmp/evaluation/370065-1177551890/tts-4-0 /tmp/evaluation/370065-1177551890/instance-370065-1177551890.cnf 
0.50/0.58	c CPU limit set to 5000.000000
0.50/0.58	c Variables = 322
0.50/0.58	c Clauses = 9322
0.50/0.58	c Literals = 72335
0.50/0.58	c Reduced size:
0.50/0.58	c Variables = 322
0.50/0.58	c Clauses = 9321
0.50/0.58	c Literals = 72333
0.50/0.58	c Independent sub-problems = 1
0.50/0.58	c Sub-problem with 321 variables
0.50/0.58	c using permutation method 4
0.50/0.58	c Ordering finished 0.210 seconds
0.50/0.58	c mapped 0.220 seconds
0.50/0.58	c permuted 0.220 seconds
0.50/0.58	c init finished 0.240 seconds
0.50/0.58	c tree built 0.310 seconds
0.50/0.58	c Partial assignments = 19098, improvements = 4967
0.50/0.58	s UNSATISFIABLE
0.50/0.58	c Time = 0.58 seconds

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node34/watcher-370065-1177551890 -o ROOT/results/node34/solver-370065-1177551890 -C 5000 -W 7500 -M 1800 --output-limit 1,15 /tmp/evaluation/370065-1177551890/tts-4-0 /tmp/evaluation/370065-1177551890/instance-370065-1177551890.cnf 

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): 7500 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.93 1.02 0.96 3/77 567
/proc/meminfo: memFree=1686520/2055920 swapFree=4159680/4192956
[pid=567] ppid=565 vsize=796 CPUtime=0
/proc/567/stat : 567 (tts-4-0) R 565 567 32518 0 -1 4194304 106 0 0 0 0 0 0 0 18 0 1 0 203104463 815104 92 18446744073709551615 134512640 134976056 4294956672 18446744073709551615 134627035 0 0 4096 0 0 0 0 17 1 0 0
/proc/567/statm: 199 93 57 113 0 83 0

[startup+0.0372301 s]
/proc/loadavg: 0.93 1.02 0.96 3/77 567
/proc/meminfo: memFree=1686520/2055920 swapFree=4159680/4192956
[pid=567] ppid=565 vsize=1628 CPUtime=0.03
/proc/567/stat : 567 (tts-4-0) R 565 567 32518 0 -1 4194304 315 0 0 0 3 0 0 0 18 0 1 0 203104463 1667072 301 18446744073709551615 134512640 134976056 4294956672 18446744073709551615 134518044 0 0 4096 0 0 0 0 17 1 0 0
/proc/567/statm: 407 301 58 113 0 291 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 1628

[startup+0.101234 s]
/proc/loadavg: 0.93 1.02 0.96 3/77 567
/proc/meminfo: memFree=1686520/2055920 swapFree=4159680/4192956
[pid=567] ppid=565 vsize=2980 CPUtime=0.09
/proc/567/stat : 567 (tts-4-0) R 565 567 32518 0 -1 4194304 621 0 0 0 9 0 0 0 18 0 1 0 203104463 3051520 607 18446744073709551615 134512640 134976056 4294956672 18446744073709551615 134627035 0 0 4096 0 0 0 0 17 1 0 0
/proc/567/statm: 745 607 62 113 0 629 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2980

[startup+0.30125 s]
/proc/loadavg: 0.93 1.02 0.96 3/77 567
/proc/meminfo: memFree=1686520/2055920 swapFree=4159680/4192956
[pid=567] ppid=565 vsize=6432 CPUtime=0.3
/proc/567/stat : 567 (tts-4-0) R 565 567 32518 0 -1 4194304 1505 0 0 0 29 1 0 0 19 0 1 0 203104463 6586368 1489 18446744073709551615 134512640 134976056 4294956672 18446744073709551615 134627035 0 0 4096 0 0 0 0 17 1 0 0
/proc/567/statm: 1608 1489 65 113 0 1492 0
Current children cumulated CPU time (s) 0.3
Current children cumulated vsize (KiB) 6432

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

[startup+0.501266 s]
/proc/loadavg: 0.93 1.02 0.96 3/77 567
/proc/meminfo: memFree=1686520/2055920 swapFree=4159680/4192956
[pid=567] ppid=565 vsize=7120 CPUtime=0.5
/proc/567/stat : 567 (tts-4-0) R 565 567 32518 0 -1 4194304 1712 0 0 0 49 1 0 0 21 0 1 0 203104463 7290880 1696 18446744073709551615 134512640 134976056 4294956672 18446744073709551615 134591678 0 0 4096 0 0 0 0 17 1 0 0
/proc/567/statm: 1780 1696 66 113 0 1664 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 7120

Child status: 20
Real time (s): 0.59083
CPU time (s): 0.59091
CPU user time (s): 0.577912
CPU system time (s): 0.012998
CPU usage (%): 100.014
Max. virtual memory (cumulated for all children) (KiB): 7120

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

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node34 on Thu Apr 26 01:44:50 UTC 2007

IDJOB= 370065
IDBENCH= 24582
IDSOLVER= 178
FILE ID= node34/370065-1177551890

PBS_JOBID= 4696623

Free space on /tmp= 66425 MiB

SOLVER NAME= TTS 4.0
BENCH NAME= HOME/pub/bench/SAT07/crafted/Medium/contest05/pebbling/unsat-pbl-00090.sat05-1326.reshuffled-07.cnf
COMMAND LINE= /tmp/evaluation/370065-1177551890/tts-4-0 /tmp/evaluation/370065-1177551890/instance-370065-1177551890.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node34/watcher-370065-1177551890 -o ROOT/results/node34/solver-370065-1177551890 -C 5000 -W 7500 -M 1800 --output-limit 1,15  /tmp/evaluation/370065-1177551890/tts-4-0 /tmp/evaluation/370065-1177551890/instance-370065-1177551890.cnf            

META MD5SUM SOLVER= d41d8cd98f00b204e9800998ecf8427e
MD5SUM BENCH=  fc73c241ff6e8e1a49a6ff2500eb7905

RANDOM SEED= 271380486

TIME LIMIT= 5000 seconds
MEMORY LIMIT= 1800 MiB

Linux node34.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.236
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.236
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:       1686992 kB
Buffers:         35760 kB
Cached:         212020 kB
SwapCached:       3072 kB
Active:         216712 kB
Inactive:        92700 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1686992 kB
SwapTotal:     4192956 kB
SwapFree:      4159680 kB
Dirty:            1004 kB
Writeback:           0 kB
Mapped:          68516 kB
Slab:            44744 kB
Committed_AS:  1670656 kB
PageTables:       2068 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= 66425 MiB

End job on node34 on Thu Apr 26 01:44:51 UTC 2007