Trace number 1797777

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
minisat2-core 070721UNSAT 0.181972 0.182238

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.129979
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	This is MiniSat 2.0 beta
0.00/0.00	WARNING: for repeatability, setting FPU to use double precision
0.00/0.00	============================[ Problem Statistics ]=============================
0.00/0.00	|                                                                             |
0.00/0.00	|  Number of variables:  110923                                               |
0.00/0.00	|  Number of clauses:    286428                                               |
0.09/0.17	|  Parsing time:         0.15         s                                       |
0.09/0.17	Solved by unit propagation
0.09/0.17	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-1797777-1242076413/watcher-1797777-1242076413 -o /tmp/evaluation-result-1797777-1242076413/solver-1797777-1242076413 -C 1200 -W 1800 -M 1800 minisat_static HOME/instance-1797777-1242076413.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): 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.99 0.98 1.00 3/64 6561
/proc/meminfo: memFree=927568/2055920 swapFree=3990764/4192956
[pid=6561] ppid=6559 vsize=2728 CPUtime=0
/proc/6561/stat : 6561 (minisat_static) R 6559 6561 6303 0 -1 4194304 516 0 0 0 0 0 0 0 18 0 1 0 235674871 2793472 501 1992294400 134512640 135213614 4294956256 18446744073709551615 134524639 0 0 4096 3 0 0 0 17 1 0 0
/proc/6561/statm: 682 503 58 171 0 508 0

[startup+0.0127869 s]
/proc/loadavg: 0.99 0.98 1.00 3/64 6561
/proc/meminfo: memFree=927568/2055920 swapFree=3990764/4192956
[pid=6561] ppid=6559 vsize=4864 CPUtime=0
/proc/6561/stat : 6561 (minisat_static) R 6559 6561 6303 0 -1 4194304 1017 0 0 0 0 0 0 0 18 0 1 0 235674871 4980736 1002 1992294400 134512640 135213614 4294956256 18446744073709551615 134524828 0 0 4096 3 0 0 0 17 1 0 0
/proc/6561/statm: 1216 1003 58 171 0 1042 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 4864

[startup+0.101797 s]
/proc/loadavg: 0.99 0.98 1.00 3/64 6561
/proc/meminfo: memFree=927568/2055920 swapFree=3990764/4192956
[pid=6561] ppid=6559 vsize=14960 CPUtime=0.09
/proc/6561/stat : 6561 (minisat_static) R 6559 6561 6303 0 -1 4194304 3244 0 0 0 7 2 0 0 18 0 1 0 235674871 15319040 3166 1992294400 134512640 135213614 4294956256 18446744073709551615 134719510 0 0 4096 3 0 0 0 17 1 0 0
/proc/6561/statm: 3740 3167 58 171 0 3566 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 14960

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

Child status: 20
Real time (s): 0.182238
CPU time (s): 0.181972
CPU user time (s): 0.149977
CPU system time (s): 0.031995
CPU usage (%): 99.8541
Max. virtual memory (cumulated for all children) (KiB): 14960

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

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node23 at 2009-05-11 23:13:34
IDJOB=1797777
IDBENCH=20516
IDSOLVER=651
FILE ID=node23/1797777-1242076413
PBS_JOBID= 9277591
Free space on /tmp= 66424 MiB

SOLVER NAME= minisat2-core 070721
BENCH NAME= SAT07/industrial/babic/xinetd/xinetd_vc56703.cnf
COMMAND LINE= minisat_static BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1797777-1242076413/watcher-1797777-1242076413 -o /tmp/evaluation-result-1797777-1242076413/solver-1797777-1242076413 -C 1200 -W 1800 -M 1800  minisat_static HOME/instance-1797777-1242076413.cnf

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

MD5SUM BENCH= 09053ffc48c8fbc3352a0ce4d89c2bbb
RANDOM SEED=510853806

node23.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.238
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.238
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:        928048 kB
Buffers:         67520 kB
Cached:         799412 kB
SwapCached:     196860 kB
Active:         207896 kB
Inactive:       857452 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        928048 kB
SwapTotal:     4192956 kB
SwapFree:      3990764 kB
Dirty:            5884 kB
Writeback:           0 kB
Mapped:          14008 kB
Slab:            48600 kB
Committed_AS:   829476 kB
PageTables:       1388 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= 66424 MiB
End job on node23 at 2009-05-11 23:13:34