Trace number 318909

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 3.14852 3.15133

General information on the benchmark

Nameindustrial/babic/hsatv17/
hsat_vc11817.cnf
MD5SUMec98bb92b9928019088745bf76777cb6
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.79273
Satisfiable
(Un)Satisfiability was proved
Number of variables240300
Number of clauses691064
Sum of the clauses size1797915
Maximum clause length3
Minimum clause length1
Number of clauses of size 128020
Number of clauses of size 2219237
Number of clauses of size 3443807
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:  240349                                               |
0.00/0.00	|  Number of clauses:    691064                                               |
1.89/1.95	|  Parsing time:         1.85         s                                       |
3.09/3.13	lookaheads            : 0
3.09/3.13	variable balance      : 0.00
3.09/3.13	restarts              : 0
3.09/3.13	conflicts             : 0              (0 /sec)
3.09/3.13	decisions             : 0              ( nan % random) (0 /sec)
3.09/3.13	decision = positive   : 0
3.09/3.13	decision = negative   : 0
3.09/3.13	propagations          : 31057          (10292 /sec)
3.09/3.13	conflict literals     : 0              ( nan % deleted)
3.09/3.13	Memory used           : 88.38 MB
3.09/3.13	CPU time              : 3.01754 s
3.09/3.13	
3.09/3.13	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/node4/watcher-318909-1176323171 -o ROOT/results/node4/solver-318909-1176323171 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/318909-1176323171/minimarch /tmp/evaluation/318909-1176323171/instance-318909-1176323171.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: 0.85 0.96 0.98 3/77 5628
/proc/meminfo: memFree=1651992/2055920 swapFree=4192956/4192956
[pid=5628] ppid=5626 vsize=2460 CPUtime=0
/proc/5628/stat : 5628 (minimarch) R 5626 5628 4640 0 -1 4194304 517 0 0 0 0 0 0 0 18 0 1 0 108354923 2519040 501 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134553814 0 0 4096 3 0 0 0 17 1 0 0
/proc/5628/statm: 615 502 51 132 0 480 0

[startup+0.0499589 s]
/proc/loadavg: 0.85 0.96 0.98 3/77 5628
/proc/meminfo: memFree=1651992/2055920 swapFree=4192956/4192956
[pid=5628] ppid=5626 vsize=14780 CPUtime=0.04
/proc/5628/stat : 5628 (minimarch) R 5626 5628 4640 0 -1 4194304 3057 0 0 0 3 1 0 0 18 0 1 0 108354923 15134720 3025 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134526723 0 0 4096 3 0 0 0 17 1 0 0
/proc/5628/statm: 3695 3027 51 132 0 3560 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 14780

[startup+0.101963 s]
/proc/loadavg: 0.85 0.96 0.98 3/77 5628
/proc/meminfo: memFree=1651992/2055920 swapFree=4192956/4192956
[pid=5628] ppid=5626 vsize=30824 CPUtime=0.09
/proc/5628/stat : 5628 (minimarch) R 5626 5628 4640 0 -1 4194304 6065 0 0 0 6 3 0 0 18 0 1 0 108354923 31563776 5999 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134526723 0 0 4096 3 0 0 0 17 1 0 0
/proc/5628/statm: 7706 5999 51 132 0 7571 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 30824

[startup+0.301982 s]
/proc/loadavg: 0.85 0.96 0.98 3/77 5628
/proc/meminfo: memFree=1651992/2055920 swapFree=4192956/4192956
[pid=5628] ppid=5626 vsize=45408 CPUtime=0.29
/proc/5628/stat : 5628 (minimarch) R 5626 5628 4640 0 -1 4194304 9189 0 0 0 24 5 0 0 19 0 1 0 108354923 46497792 9123 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/5628/statm: 11352 9124 51 132 0 11217 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 45408

[startup+0.70202 s]
/proc/loadavg: 0.85 0.96 0.98 3/77 5628
/proc/meminfo: memFree=1651992/2055920 swapFree=4192956/4192956
[pid=5628] ppid=5626 vsize=69052 CPUtime=0.69
/proc/5628/stat : 5628 (minimarch) R 5626 5628 4640 0 -1 4194304 14942 0 0 0 62 7 0 0 23 0 1 0 108354923 70709248 14876 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/5628/statm: 17263 14877 51 132 0 17128 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 69052

[startup+1.5011 s]
/proc/loadavg: 0.85 0.96 0.98 2/78 5629
/proc/meminfo: memFree=1586576/2055920 swapFree=4192956/4192956
[pid=5628] ppid=5626 vsize=73712 CPUtime=1.49
/proc/5628/stat : 5628 (minimarch) R 5626 5628 4640 0 -1 4194304 16295 0 0 0 140 9 0 0 25 0 1 0 108354923 75481088 16229 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134523055 0 0 4096 3 0 0 0 17 1 0 0
/proc/5628/statm: 18428 16229 51 132 0 18293 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 73712

[startup+3.10125 s]
/proc/loadavg: 0.85 0.96 0.98 2/78 5629
/proc/meminfo: memFree=1586704/2055920 swapFree=4192956/4192956
[pid=5628] ppid=5626 vsize=92840 CPUtime=3.09
/proc/5628/stat : 5628 (minimarch) R 5626 5628 4640 0 -1 4194304 20656 0 0 0 298 11 0 0 25 0 1 0 108354923 95068160 20590 18446744073709551615 134512640 135054332 4294956592 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/5628/statm: 23210 20590 62 132 0 23075 0
Current children cumulated CPU time (s) 3.09
Current children cumulated vsize (KiB) 92840

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

Child status: 20
Real time (s): 3.15133
CPU time (s): 3.14852
CPU user time (s): 3.01754
CPU system time (s): 0.13098
CPU usage (%): 99.9109
Max. virtual memory (cumulated for all children) (KiB): 92840

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

runsolver used 0.006998 second user time and 0.014997 second system time

The end

Launcher Data (download as text)

Begin job on node4 on Wed Apr 11 20:26:12 UTC 2007

IDJOB= 318909
IDBENCH= 20466
IDSOLVER= 110
FILE ID= node4/318909-1176323171

PBS_JOBID= 4516503

Free space on /tmp= 66545 MiB

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

META MD5SUM SOLVER= cd0143c15836d32fe9acb8d523a59b67
MD5SUM BENCH=  ec98bb92b9928019088745bf76777cb6

RANDOM SEED= 901045912

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node4.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.218
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.218
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:       1652464 kB
Buffers:         38472 kB
Cached:         240260 kB
SwapCached:          0 kB
Active:         227588 kB
Inactive:       110636 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1652464 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:           16020 kB
Writeback:           0 kB
Mapped:          78340 kB
Slab:            50792 kB
Committed_AS:  4003768 kB
PageTables:       1816 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= 66545 MiB

End job on node4 on Wed Apr 11 20:26:15 UTC 2007