Trace number 1832120

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
MiniSAT 09z 2009-03-22UNSAT 0.298954 0.298585

General information on the benchmark

Nameindustrial/babic/xinetd/
xinetd_vc56703.cnf
MD5SUM09053ffc48c8fbc3352a0ce4d89c2bbb
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.217966
Satisfiable
(Un)Satisfiability was proved
Number of variables110923
Number of clauses286428
Sum of the clauses size694958
Maximum clause length3
Minimum clause length1
Number of clauses of size 113085
Number of clauses of size 2138156
Number of clauses of size 3135187
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.00/0.00	c Parsing...
0.00/0.24	c ==============================================================================
0.00/0.24	c |           |     ORIGINAL     |              LEARNT              |          |
0.00/0.24	c | Conflicts | Clauses Literals |   Limit Clauses Literals  Lit/Cl | Progress |
0.00/0.24	c ==============================================================================
0.00/0.24	c |         0 |  270567   676320 |   81170       0        0     nan |  0.000 % |
0.00/0.28	c (contradiction during subsumption)
0.00/0.28	c starts                :        0
0.00/0.28	c conflicts             :        0   (0 /sec)
0.00/0.28	c reduce learnts        :        0   (0 /sec)
0.00/0.28	c decisions             :        0   (0 /sec)
0.00/0.28	c propagations          :        0   (0 /sec)
0.00/0.28	c inspects              :        0   (0 /sec)
0.00/0.28	c memory used           :  41.4414 MB
0.00/0.28	c CPU time              : 0.239963 s
0.00/0.28	c 
0.00/0.29	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-1832120-1242769197/watcher-1832120-1242769197 -o /tmp/evaluation-result-1832120-1242769197/solver-1832120-1242769197 -C 1200 -W 1800 -M 1800 SatELiteGTI HOME/instance-1832120-1242769197.cnf -random-seed=1555820526 

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): 1800 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: 0.89 0.95 0.90 3/64 12033
/proc/meminfo: memFree=1972376/2055920 swapFree=4180280/4192956
[pid=12033] ppid=12031 vsize=5356 CPUtime=0
/proc/12033/stat : 12033 (SatELiteGTI) R 12031 12033 11849 0 -1 4194304 292 250 0 0 0 0 0 0 18 0 1 0 304952954 5484544 237 1992294400 4194304 4889804 548682068800 18446744073709551615 273952598687 0 65538 4100 65536 0 0 0 17 0 0 0
/proc/12033/statm: 1339 237 197 169 0 50 0

[startup+0.0534171 s]
/proc/loadavg: 0.89 0.95 0.90 3/64 12033
/proc/meminfo: memFree=1972376/2055920 swapFree=4180280/4192956
[pid=12033] ppid=12031 vsize=5356 CPUtime=0
/proc/12033/stat : 12033 (SatELiteGTI) S 12031 12033 11849 0 -1 4194304 310 250 0 0 0 0 0 0 19 0 1 0 304952954 5484544 237 1992294400 4194304 4889804 548682068800 18446744073709551615 273952596804 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/12033/statm: 1339 237 197 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.101422 s]
/proc/loadavg: 0.89 0.95 0.90 3/64 12033
/proc/meminfo: memFree=1972376/2055920 swapFree=4180280/4192956
[pid=12033] ppid=12031 vsize=5356 CPUtime=0
/proc/12033/stat : 12033 (SatELiteGTI) S 12031 12033 11849 0 -1 4194304 310 250 0 0 0 0 0 0 19 0 1 0 304952954 5484544 237 1992294400 4194304 4889804 548682068800 18446744073709551615 273952596804 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/12033/statm: 1339 237 197 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

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

[startup+0.201434 s]
/proc/loadavg: 0.89 0.95 0.90 3/64 12033
/proc/meminfo: memFree=1972376/2055920 swapFree=4180280/4192956
[pid=12033] ppid=12031 vsize=5356 CPUtime=0
/proc/12033/stat : 12033 (SatELiteGTI) S 12031 12033 11849 0 -1 4194304 310 250 0 0 0 0 0 0 19 0 1 0 304952954 5484544 237 1992294400 4194304 4889804 548682068800 18446744073709551615 273952596804 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/12033/statm: 1339 237 197 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

Child status: 20
Real time (s): 0.298585
CPU time (s): 0.298954
CPU user time (s): 0.242963
CPU system time (s): 0.055991
CPU usage (%): 100.124
Max. virtual memory (cumulated for all children) (KiB): 5356

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.242963
system time used= 0.055991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 10562
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= 15
involuntary context switches= 8

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node20 at 2009-05-19 23:39:57
IDJOB=1832120
IDBENCH=20516
IDSOLVER=672
FILE ID=node20/1832120-1242769197
PBS_JOBID= 9322278
Free space on /tmp= 66248 MiB

SOLVER NAME= MiniSAT 09z 2009-03-22
BENCH NAME= SAT07/industrial/babic/xinetd/xinetd_vc56703.cnf
COMMAND LINE= SatELiteGTI BENCHNAME -random-seed=RANDOMSEED
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1832120-1242769197/watcher-1832120-1242769197 -o /tmp/evaluation-result-1832120-1242769197/solver-1832120-1242769197 -C 1200 -W 1800 -M 1800  SatELiteGTI HOME/instance-1832120-1242769197.cnf -random-seed=1555820526

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

MD5SUM BENCH= 09053ffc48c8fbc3352a0ce4d89c2bbb
RANDOM SEED=1555820526

node20.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.214
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	: 5931.00
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.214
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:       1972928 kB
Buffers:         10000 kB
Cached:          36564 kB
SwapCached:       6816 kB
Active:          23808 kB
Inactive:        30988 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1972928 kB
SwapTotal:     4192956 kB
SwapFree:      4180280 kB
Dirty:            6556 kB
Writeback:           0 kB
Mapped:          13464 kB
Slab:            14304 kB
Committed_AS:  1130016 kB
PageTables:       1400 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= 66248 MiB
End job on node20 at 2009-05-19 23:39:58