Trace number 1784668

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
VARSAT-industrial 2009-03-22UNSAT 0.328949 0.329982

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.128979
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 

0.00/0.00	c ============================[ Problem Statistics ]=============================
0.00/0.00	c |                                                                             |
0.00/0.00	c |  Number of variables:  322                                                  |
0.00/0.00	c |  Number of clauses:    9322                                                 |
0.00/0.02	c |  Parsing time:         0.02         s                                       |
0.00/0.02	c |  Timeout:              43200 s
0.00/0.02	c |  Random Seed:          1685962052.000000
0.00/0.02	c |  Heuristic:            EMBP-G, threshold 0.950                              |
0.00/0.02	c |  Branching Rule:       default (solution-guided)                            |
0.00/0.02	c |  Learned clauses in surveys?  Using NO learned clauses.                     |
0.00/0.02	c |                                                                             |
0.29/0.32	c surveys--CPU time (sec)   : 0.0000         (0.00 % of total)
0.29/0.32	c surveys--attempted        : 0              (nan /sec)
0.29/0.32	c surveys--converged        : 0              ( nan % successful)
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          : 22             (68 /sec)
0.29/0.32	c conflict literals     : 0              ( nan % deleted)
0.29/0.32	c Memory used           : 6.39 MB
0.29/0.32	c Total CPU time (sec)      : 0.3250      
0.29/0.32	c 
0.29/0.32	s UNSATISFIABLE

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1784668-1241864158/watcher-1784668-1241864158 -o /tmp/evaluation-result-1784668-1241864158/solver-1784668-1241864158 -C 5000 -W 6000 -M 1800 HOME/varsat-industrial_static -seed=1685962052 HOME/instance-1784668-1241864158.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): 6000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.01 0.99 0.88 3/65 27314
/proc/meminfo: memFree=1834528/2055920 swapFree=4162540/4192956
[pid=27314] ppid=27312 vsize=2544 CPUtime=0
/proc/27314/stat : 27314 (varsat-industri) R 27312 27314 26795 0 -1 4194304 305 0 0 0 0 0 0 0 20 0 1 0 214444741 2605056 290 1992294400 4194304 5102648 548682068784 18446744073709551615 4491703 0 0 4096 3 0 0 0 17 1 0 0
/proc/27314/statm: 636 291 87 221 0 412 0

[startup+0.103097 s]
/proc/loadavg: 1.01 0.99 0.88 3/65 27314
/proc/meminfo: memFree=1834528/2055920 swapFree=4162540/4192956
[pid=27314] ppid=27312 vsize=5404 CPUtime=0.09
/proc/27314/stat : 27314 (varsat-industri) R 27312 27314 26795 0 -1 4194304 1024 0 0 0 9 0 0 0 20 0 1 0 214444741 5533696 1009 1992294400 4194304 5102648 548682068784 18446744073709551615 4273065 0 0 4096 3 0 0 0 17 1 0 0
/proc/27314/statm: 1351 1009 100 221 0 1127 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5404

[startup+0.201115 s]
/proc/loadavg: 1.01 0.99 0.88 3/65 27314
/proc/meminfo: memFree=1834528/2055920 swapFree=4162540/4192956
[pid=27314] ppid=27312 vsize=6008 CPUtime=0.19
/proc/27314/stat : 27314 (varsat-industri) R 27312 27314 26795 0 -1 4194304 1181 0 0 0 19 0 0 0 21 0 1 0 214444741 6152192 1166 1992294400 4194304 5102648 548682068784 18446744073709551615 4272872 0 0 4096 3 0 0 0 17 1 0 0
/proc/27314/statm: 1502 1166 100 221 0 1278 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 6008

[startup+0.301137 s]
/proc/loadavg: 1.01 0.99 0.88 3/65 27314
/proc/meminfo: memFree=1834528/2055920 swapFree=4162540/4192956
[pid=27314] ppid=27312 vsize=6248 CPUtime=0.29
/proc/27314/stat : 27314 (varsat-industri) R 27312 27314 26795 0 -1 4194304 1242 0 0 0 29 0 0 0 22 0 1 0 214444741 6397952 1227 1992294400 4194304 5102648 548682068784 18446744073709551615 4266490 0 0 4096 3 0 0 0 17 1 0 0
/proc/27314/statm: 1562 1227 100 221 0 1338 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 6248

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

[startup+0.301137 s]
/proc/loadavg: 1.01 0.99 0.88 3/65 27314
/proc/meminfo: memFree=1834528/2055920 swapFree=4162540/4192956
[pid=27314] ppid=27312 vsize=6248 CPUtime=0.29
/proc/27314/stat : 27314 (varsat-industri) R 27312 27314 26795 0 -1 4194304 1242 0 0 0 29 0 0 0 22 0 1 0 214444741 6397952 1227 1992294400 4194304 5102648 548682068784 18446744073709551615 4266490 0 0 4096 3 0 0 0 17 1 0 0
/proc/27314/statm: 1562 1227 100 221 0 1338 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 6248

Child status: 20
Real time (s): 0.329982
CPU time (s): 0.328949
CPU user time (s): 0.32495
CPU system time (s): 0.003999
CPU usage (%): 99.6869
Max. virtual memory (cumulated for all children) (KiB): 6248

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

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node80 at 2009-05-09 12:15:58
IDJOB=1784668
IDBENCH=24582
IDSOLVER=641
FILE ID=node80/1784668-1241864158
PBS_JOBID= 9264537
Free space on /tmp= 65860 MiB

SOLVER NAME= VARSAT-industrial 2009-03-22
BENCH NAME= SAT07/crafted/Medium/contest05/pebbling/unsat-pbl-00090.sat05-1326.reshuffled-07.cnf
COMMAND LINE= HOME/varsat-industrial_static -seed=RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1784668-1241864158/watcher-1784668-1241864158 -o /tmp/evaluation-result-1784668-1241864158/solver-1784668-1241864158 -C 5000 -W 6000 -M 1800  HOME/varsat-industrial_static -seed=1685962052 HOME/instance-1784668-1241864158.cnf

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

MD5SUM BENCH= fc73c241ff6e8e1a49a6ff2500eb7905
RANDOM SEED=1685962052

node80.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.270
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.270
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1835008 kB
Buffers:         31152 kB
Cached:         102216 kB
SwapCached:      25208 kB
Active:          70096 kB
Inactive:        90648 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1835008 kB
SwapTotal:     4192956 kB
SwapFree:      4162540 kB
Dirty:            1324 kB
Writeback:           0 kB
Mapped:          13456 kB
Slab:            46072 kB
Committed_AS:   740944 kB
PageTables:       1384 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= 65856 MiB
End job on node80 at 2009-05-09 12:15:58