Trace number 320713

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
minimarch 2007-02-08UNSAT 0.748885 0.750333

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.196969
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	This is MiniMarch, a modified version of 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:  110822                                               |
0.00/0.00	|  Number of clauses:    286158                                               |
0.69/0.73	|  Parsing time:         0.71         s                                       |
0.69/0.74	Solved by unit propagation
0.69/0.74	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/node11/watcher-320713-1176323676 -o ROOT/results/node11/solver-320713-1176323676 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/320713-1176323676/minimarch /tmp/evaluation/320713-1176323676/instance-320713-1176323676.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.69 1.61 1.23 3/77 31911
/proc/meminfo: memFree=1199864/2055920 swapFree=4192952/4192956
[pid=31911] ppid=31909 vsize=2492 CPUtime=0
/proc/31911/stat : 31911 (minimarch) R 31909 31911 30795 0 -1 4194304 532 0 0 0 0 0 0 0 18 0 1 0 73416607 2551808 516 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134526285 0 0 4096 3 0 0 0 17 1 0 0
/proc/31911/statm: 623 518 51 132 0 488 0

[startup+0.0646071 s]
/proc/loadavg: 1.69 1.61 1.23 3/77 31911
/proc/meminfo: memFree=1199864/2055920 swapFree=4192952/4192956
[pid=31911] ppid=31909 vsize=16676 CPUtime=0.06
/proc/31911/stat : 31911 (minimarch) R 31909 31911 30795 0 -1 4194304 3310 0 0 0 5 1 0 0 18 0 1 0 73416607 17076224 3285 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/31911/statm: 4169 3285 51 132 0 4034 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 16676

[startup+0.10161 s]
/proc/loadavg: 1.69 1.61 1.23 3/77 31911
/proc/meminfo: memFree=1199864/2055920 swapFree=4192952/4192956
[pid=31911] ppid=31909 vsize=19100 CPUtime=0.09
/proc/31911/stat : 31911 (minimarch) R 31909 31911 30795 0 -1 4194304 3857 0 0 0 8 1 0 0 18 0 1 0 73416607 19558400 3832 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/31911/statm: 4775 3833 51 132 0 4640 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 19100

[startup+0.301634 s]
/proc/loadavg: 1.69 1.61 1.23 3/77 31911
/proc/meminfo: memFree=1199864/2055920 swapFree=4192952/4192956
[pid=31911] ppid=31909 vsize=30824 CPUtime=0.29
/proc/31911/stat : 31911 (minimarch) R 31909 31911 30795 0 -1 4194304 6714 0 0 0 27 2 0 0 19 0 1 0 73416607 31563776 6689 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/31911/statm: 7706 6691 51 132 0 7571 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 30824

[startup+0.70168 s]
/proc/loadavg: 1.69 1.61 1.23 3/77 31911
/proc/meminfo: memFree=1199864/2055920 swapFree=4192952/4192956
[pid=31911] ppid=31909 vsize=32276 CPUtime=0.69
/proc/31911/stat : 31911 (minimarch) R 31909 31911 30795 0 -1 4194304 7140 0 0 0 66 3 0 0 23 0 1 0 73416607 33050624 7115 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134523040 0 0 4096 3 0 0 0 17 1 0 0
/proc/31911/statm: 8069 7115 51 132 0 7934 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 32276

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

Child status: 20
Real time (s): 0.750333
CPU time (s): 0.748885
CPU user time (s): 0.712891
CPU system time (s): 0.035994
CPU usage (%): 99.807
Max. virtual memory (cumulated for all children) (KiB): 32276

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

runsolver used 0.004999 second user time and 0.001999 second system time

The end

Launcher Data (download as text)

Begin job on node11 on Wed Apr 11 20:34:37 UTC 2007

IDJOB= 320713
IDBENCH= 20510
IDSOLVER= 110
FILE ID= node11/320713-1176323676

PBS_JOBID= 4516508

Free space on /tmp= 66466 MiB

SOLVER NAME= minimarch 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/industrial/babic/xinetd/xinetd_vc56687.cnf
COMMAND LINE= /tmp/evaluation/320713-1176323676/minimarch /tmp/evaluation/320713-1176323676/instance-320713-1176323676.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node11/watcher-320713-1176323676 -o ROOT/results/node11/solver-320713-1176323676 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/320713-1176323676/minimarch /tmp/evaluation/320713-1176323676/instance-320713-1176323676.cnf            

META MD5SUM SOLVER= cd0143c15836d32fe9acb8d523a59b67
MD5SUM BENCH=  8ee40e47d0f78a39fcf5c18ad73a5bdd

RANDOM SEED= 502806969

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node11.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.235
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.235
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:       1200336 kB
Buffers:         41272 kB
Cached:         688228 kB
SwapCached:          4 kB
Active:         249892 kB
Inactive:       534216 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1200336 kB
SwapTotal:     4192956 kB
SwapFree:      4192952 kB
Dirty:            7420 kB
Writeback:           0 kB
Mapped:          73476 kB
Slab:            56972 kB
Committed_AS:  5049348 kB
PageTables:       1848 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= 66466 MiB

End job on node11 on Wed Apr 11 20:34:38 UTC 2007