Trace number 422062

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 2007UNSAT 0.326949 0.329219

General information on the benchmark

Nameindustrial/babic/xinetd/
xinetd_vc56687.cnf
MD5SUM8ee40e47d0f78a39fcf5c18ad73a5bdd
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.194969
Satisfiable
(Un)Satisfiability was proved
Number of variables110822
Number of clauses286158
Sum of the clauses size694158
Maximum clause length3
Minimum clause length1
Number of clauses of size 113085
Number of clauses of size 2138146
Number of clauses of size 3134927
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

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:  110822                                               |
0.00/0.00	c |  Number of clauses:    286158                                               |
0.29/0.32	c |  Parsing time:         0.28         s                                       |
0.29/0.32	c Solved by unit propagation
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.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node6/watcher-422062-1177543165 -o ROOT/results/node6/solver-422062-1177543165 -C 10000 -W 15000 -M 1800 --output-limit 1,15 /tmp/evaluation/422062-1177543165/minisat_noassertions /tmp/evaluation/422062-1177543165/instance-422062-1177543165.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 10000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 10030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 15000 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.12 0.99 0.63 3/77 29621
/proc/meminfo: memFree=1795960/2055924 swapFree=4143416/4192956
[pid=29621] ppid=29619 vsize=2476 CPUtime=0
/proc/29621/stat : 29621 (minisat_noasser) R 29619 29621 29365 0 -1 4194304 524 0 0 0 0 0 0 0 18 0 1 0 230354220 2535424 510 18446744073709551615 134512640 135048876 4294956640 18446744073709551615 134524455 0 0 4096 3 0 0 0 17 1 0 0
/proc/29621/statm: 619 511 50 130 0 486 0

[startup+0.074803 s]
/proc/loadavg: 1.12 0.99 0.63 3/77 29621
/proc/meminfo: memFree=1795960/2055924 swapFree=4143416/4192956
[pid=29621] ppid=29619 vsize=17088 CPUtime=0.07
/proc/29621/stat : 29621 (minisat_noasser) R 29619 29621 29365 0 -1 4194304 3430 0 0 0 6 1 0 0 18 0 1 0 230354220 17498112 3406 18446744073709551615 134512640 135048876 4294956640 18446744073709551615 134683871 0 0 4096 3 0 0 0 17 1 0 0
/proc/29621/statm: 4272 3406 50 130 0 4139 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 17088

[startup+0.101806 s]
/proc/loadavg: 1.12 0.99 0.63 3/77 29621
/proc/meminfo: memFree=1795960/2055924 swapFree=4143416/4192956
[pid=29621] ppid=29619 vsize=18764 CPUtime=0.09
/proc/29621/stat : 29621 (minisat_noasser) R 29619 29621 29365 0 -1 4194304 3831 0 0 0 8 1 0 0 18 0 1 0 230354220 19214336 3807 18446744073709551615 134512640 135048876 4294956640 18446744073709551615 134683871 0 0 4096 3 0 0 0 17 1 0 0
/proc/29621/statm: 4691 3809 50 130 0 4558 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 18764

[startup+0.301829 s]
/proc/loadavg: 1.12 0.99 0.63 3/77 29621
/proc/meminfo: memFree=1795960/2055924 swapFree=4143416/4192956
[pid=29621] ppid=29619 vsize=30740 CPUtime=0.29
/proc/29621/stat : 29621 (minisat_noasser) R 29619 29621 29365 0 -1 4194304 6747 0 0 0 26 3 0 0 19 0 1 0 230354220 31477760 6723 18446744073709551615 134512640 135048876 4294956640 18446744073709551615 134683871 0 0 4096 3 0 0 0 17 1 0 0
/proc/29621/statm: 7685 6723 50 130 0 7552 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 30740

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

Child status: 20
Real time (s): 0.329219
CPU time (s): 0.326949
CPU user time (s): 0.282956
CPU system time (s): 0.043993
CPU usage (%): 99.3105
Max. virtual memory (cumulated for all children) (KiB): 30740

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

runsolver used 0.000999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node6 on Wed Apr 25 23:19:26 UTC 2007

IDJOB= 422062
IDBENCH= 20510
IDSOLVER= 189
FILE ID= node6/422062-1177543165

PBS_JOBID= 4695924

Free space on /tmp= 66438 MiB

SOLVER NAME= minisat SAT 2007
BENCH NAME= HOME/pub/bench/SAT07/industrial/babic/xinetd/xinetd_vc56687.cnf
COMMAND LINE= /tmp/evaluation/422062-1177543165/minisat_noassertions /tmp/evaluation/422062-1177543165/instance-422062-1177543165.cnf
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-422062-1177543165 -o ROOT/results/node6/solver-422062-1177543165 -C 10000 -W 15000 -M 1800 --output-limit 1,15  /tmp/evaluation/422062-1177543165/minisat_noassertions /tmp/evaluation/422062-1177543165/instance-422062-1177543165.cnf

META MD5SUM SOLVER= d41d8cd98f00b204e9800998ecf8427e
MD5SUM BENCH=  8ee40e47d0f78a39fcf5c18ad73a5bdd

RANDOM SEED= 869396001

TIME LIMIT= 10000 seconds
MEMORY LIMIT= 1800 MiB

Linux node6.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.232
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.232
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:      2055924 kB
MemFree:       1796496 kB
Buffers:         37744 kB
Cached:         132828 kB
SwapCached:      17652 kB
Active:          89708 kB
Inactive:       126316 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1796496 kB
SwapTotal:     4192956 kB
SwapFree:      4143416 kB
Dirty:            6588 kB
Writeback:           0 kB
Mapped:          48452 kB
Slab:            28916 kB
Committed_AS:  7163168 kB
PageTables:       1840 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= 66438 MiB

End job on node6 on Wed Apr 25 23:19:26 UTC 2007