Trace number 332733

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
minisat SAT 2007 (with assertions)UNSAT 0.32295 0.323841

General information on the benchmark

Namecrafted/Medium/contest05/pebbling/
unsat-pbl-00070.sat05-1324.reshuffled-07.cnf
MD5SUMe72b4e386685e8ae3270a3d69e1ae8da
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.241962
Satisfiable
(Un)Satisfiability was proved
Number of variables257
Number of clauses7375
Sum of the clauses size62500
Maximum clause length11
Minimum clause length1
Number of clauses of size 11
Number of clauses of size 211
Number of clauses of size 346
Number of clauses of size 4119
Number of clauses of size 5300
Number of clauses of size over 56898

Solver Data (download as text)

0.00/0.00	c This is MiniSat 2.0 (Feb 1 2007, SAT-Competition version)
0.00/0.00	c ============================[ Problem Statistics ]=============================
0.00/0.00	c |                                                                             |
0.00/0.00	c |  Number of variables:  257                                                  |
0.00/0.00	c |  Number of clauses:    7375                                                 |
0.00/0.05	c |  Parsing time:         0.05         s                                       |
0.29/0.32	c restarts              : 0
0.29/0.32	c conflicts             : 0              (0 /sec)
0.29/0.32	c decisions             : 0              ( nan % random) (0 /sec)
0.29/0.32	c propagations          : 10             (31 /sec)
0.29/0.32	c conflict literals     : 0              ( nan % deleted)
0.29/0.32	c Memory used           : 2.96 MB
0.29/0.32	c CPU time              : 0.317951 s
0.29/0.32	c 
0.29/0.32	s UNSATISFIABLE

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node3/watcher-332733-1173487891 -o ROOT/results/node3/solver-332733-1173487891 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/332733-1173487891/minisat /tmp/evaluation/332733-1173487891/instance-332733-1173487891.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): 2400 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: 1.00 1.00 0.98 3/77 22719
/proc/meminfo: memFree=1576168/2055920 swapFree=4158660/4192956
[pid=22719] ppid=22717 vsize=1888 CPUtime=0
/proc/22719/stat : 22719 (minisat) R 22717 22719 21208 0 -1 4194304 190 0 0 0 0 0 0 0 18 0 1 0 368744009 1933312 174 18446744073709551615 134512640 135078472 4294956704 18446744073709551615 134707275 0 0 4096 3 0 0 0 17 1 0 0
/proc/22719/statm: 472 174 58 138 0 331 0

[startup+0.0949541 s]
/proc/loadavg: 1.00 1.00 0.98 3/77 22719
/proc/meminfo: memFree=1576168/2055920 swapFree=4158660/4192956
[pid=22719] ppid=22717 vsize=2552 CPUtime=0.09
/proc/22719/stat : 22719 (minisat) R 22717 22719 21208 0 -1 4194304 388 0 0 0 9 0 0 0 18 0 1 0 368744009 2613248 372 18446744073709551615 134512640 135078472 4294956704 18446744073709551615 134707275 0 0 4096 3 0 0 0 17 1 0 0
/proc/22719/statm: 638 372 71 138 0 497 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2552

[startup+0.101955 s]
/proc/loadavg: 1.00 1.00 0.98 3/77 22719
/proc/meminfo: memFree=1576168/2055920 swapFree=4158660/4192956
[pid=22719] ppid=22717 vsize=2728 CPUtime=0.09
/proc/22719/stat : 22719 (minisat) R 22717 22719 21208 0 -1 4194304 400 0 0 0 9 0 0 0 18 0 1 0 368744009 2793472 384 18446744073709551615 134512640 135078472 4294956704 18446744073709551615 134521397 0 0 4096 3 0 0 0 17 1 0 0
/proc/22719/statm: 682 384 71 138 0 541 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2728

[startup+0.301971 s]
/proc/loadavg: 1.00 1.00 0.98 3/77 22719
/proc/meminfo: memFree=1576168/2055920 swapFree=4158660/4192956
[pid=22719] ppid=22717 vsize=3024 CPUtime=0.29
/proc/22719/stat : 22719 (minisat) R 22717 22719 21208 0 -1 4194304 486 0 0 0 29 0 0 0 19 0 1 0 368744009 3096576 470 18446744073709551615 134512640 135078472 4294956704 18446744073709551615 134530518 0 0 4096 3 0 0 0 17 1 0 0
/proc/22719/statm: 756 470 71 138 0 615 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 3024

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

Child status: 0
Real time (s): 0.323841
CPU time (s): 0.32295
CPU user time (s): 0.318951
CPU system time (s): 0.003999
CPU usage (%): 99.7249
Max. virtual memory (cumulated for all children) (KiB): 3024

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

runsolver used 0.002999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node3 on Sat Mar 10 00:51:32 UTC 2007

IDJOB= 332733
IDBENCH= 24587
IDSOLVER= 109
FILE ID= node3/332733-1173487891

PBS_JOBID= 4101078

Free space on /tmp= 66498 MiB

SOLVER NAME= minisat SAT 2007
BENCH NAME= HOME/pub/bench/SAT07/crafted/Medium/contest05/pebbling/unsat-pbl-00070.sat05-1324.reshuffled-07.cnf
COMMAND LINE= /tmp/evaluation/332733-1173487891/minisat /tmp/evaluation/332733-1173487891/instance-332733-1173487891.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node3/watcher-332733-1173487891 -o ROOT/results/node3/solver-332733-1173487891 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/332733-1173487891/minisat /tmp/evaluation/332733-1173487891/instance-332733-1173487891.cnf            

META MD5SUM SOLVER= 120abd248b069e44985635f055606c5a
MD5SUM BENCH=  e72b4e386685e8ae3270a3d69e1ae8da

RANDOM SEED= 142241637

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node3.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.241
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.241
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:       1576640 kB
Buffers:         47324 kB
Cached:         340836 kB
SwapCached:       2568 kB
Active:         176332 kB
Inactive:       237152 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1576640 kB
SwapTotal:     4192956 kB
SwapFree:      4158660 kB
Dirty:            1148 kB
Writeback:           0 kB
Mapped:          32984 kB
Slab:            51492 kB
Committed_AS:  1489212 kB
PageTables:       1660 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= 66498 MiB

End job on node3 on Sat Mar 10 00:51:32 UTC 2007