Trace number 330124

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-08Wrong UNSAT 1.19682 1.19878

General information on the benchmark

Nameindustrial/IBM_FV_2004_30/
IBM_FV_2004_rule_batch_30_SAT_dat.k60.cnf
MD5SUM4237e8072317ac6566570c291ae71078
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark192.238
Satisfiable
(Un)Satisfiability was proved
Number of variables123224
Number of clauses512149
Sum of the clauses size1313041
Maximum clause length12
Minimum clause length1
Number of clauses of size 12072
Number of clauses of size 2362980
Number of clauses of size 396066
Number of clauses of size 418234
Number of clauses of size 510379
Number of clauses of size over 522418

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.01	|  Number of variables:  123224                                               |
0.00/0.01	|  Number of clauses:    512149                                               |
1.09/1.19	|  Parsing time:         1.12         s                                       |
1.09/1.19	Solved by unit propagation
1.09/1.19	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/node3/watcher-330124-1173157694 -o ROOT/results/node3/solver-330124-1173157694 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/330124-1173157694/minimarch /tmp/evaluation/330124-1173157694/instance-330124-1173157694.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.00 1.00 1.00 3/77 28915
/proc/meminfo: memFree=1023072/2055920 swapFree=4191880/4192956
[pid=28915] ppid=28913 vsize=1736 CPUtime=0
/proc/28915/stat : 28915 (minimarch) R 28913 28915 27299 0 -1 4194304 330 0 0 0 0 0 0 0 18 0 1 0 335724349 1777664 314 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134518501 0 0 4096 3 0 0 0 17 1 0 0
/proc/28915/statm: 434 314 45 132 0 299 0

[startup+0.09998 s]
/proc/loadavg: 1.00 1.00 1.00 3/77 28915
/proc/meminfo: memFree=1023072/2055920 swapFree=4191880/4192956
[pid=28915] ppid=28913 vsize=9152 CPUtime=0.09
/proc/28915/stat : 28915 (minimarch) R 28913 28915 27299 0 -1 4194304 2008 0 0 0 8 1 0 0 18 0 1 0 335724349 9371648 1992 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134562614 0 0 4096 3 0 0 0 17 1 0 0
/proc/28915/statm: 2288 1993 51 132 0 2153 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9152

[startup+0.10198 s]
/proc/loadavg: 1.00 1.00 1.00 3/77 28915
/proc/meminfo: memFree=1023072/2055920 swapFree=4191880/4192956
[pid=28915] ppid=28913 vsize=9152 CPUtime=0.09
/proc/28915/stat : 28915 (minimarch) R 28913 28915 27299 0 -1 4194304 2045 0 0 0 8 1 0 0 18 0 1 0 335724349 9371648 2029 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/28915/statm: 2288 2031 51 132 0 2153 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9152

[startup+0.301996 s]
/proc/loadavg: 1.00 1.00 1.00 3/77 28915
/proc/meminfo: memFree=1023072/2055920 swapFree=4191880/4192956
[pid=28915] ppid=28913 vsize=25304 CPUtime=0.29
/proc/28915/stat : 28915 (minimarch) R 28913 28915 27299 0 -1 4194304 5722 0 0 0 26 3 0 0 19 0 1 0 335724349 25911296 5706 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134526723 0 0 4096 3 0 0 0 17 1 0 0
/proc/28915/statm: 6326 5707 51 132 0 6191 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 25304

[startup+0.701029 s]
/proc/loadavg: 1.00 1.00 1.00 3/77 28915
/proc/meminfo: memFree=1023072/2055920 swapFree=4191880/4192956
[pid=28915] ppid=28913 vsize=46956 CPUtime=0.69
/proc/28915/stat : 28915 (minimarch) R 28913 28915 27299 0 -1 4194304 10782 0 0 0 63 6 0 0 23 0 1 0 335724349 48082944 10766 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134522964 0 0 4096 3 0 0 0 17 1 0 0
/proc/28915/statm: 11739 10766 51 132 0 11604 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 46956

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

[startup+1.10506 s]
/proc/loadavg: 1.00 1.00 1.00 2/78 28916
/proc/meminfo: memFree=980120/2055920 swapFree=4191880/4192956
[pid=28915] ppid=28913 vsize=46956 CPUtime=1.09
/proc/28915/stat : 28915 (minimarch) R 28913 28915 27299 0 -1 4194304 10782 0 0 0 103 6 0 0 25 0 1 0 335724349 48082944 10766 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134523361 0 0 4096 3 0 0 0 17 1 0 0
/proc/28915/statm: 11739 10766 51 132 0 11604 0
Current children cumulated CPU time (s) 1.09
Current children cumulated vsize (KiB) 46956

Child status: 20
Real time (s): 1.19878
CPU time (s): 1.19682
CPU user time (s): 1.12483
CPU system time (s): 0.071989
CPU usage (%): 99.8364
Max. virtual memory (cumulated for all children) (KiB): 46956

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

runsolver used 0.002999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node3 on Tue Mar  6 05:08:15 UTC 2007

IDJOB= 330124
IDBENCH= 20556
IDSOLVER= 110
FILE ID= node3/330124-1173157694

PBS_JOBID= 4014987

Free space on /tmp= 66518 MiB

SOLVER NAME= minimarch 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/industrial/IBM_FV_2004_30/IBM_FV_2004_rule_batch_30_SAT_dat.k60.cnf
COMMAND LINE= /tmp/evaluation/330124-1173157694/minimarch /tmp/evaluation/330124-1173157694/instance-330124-1173157694.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node3/watcher-330124-1173157694 -o ROOT/results/node3/solver-330124-1173157694 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/330124-1173157694/minimarch /tmp/evaluation/330124-1173157694/instance-330124-1173157694.cnf            

META MD5SUM SOLVER= cd0143c15836d32fe9acb8d523a59b67
MD5SUM BENCH=  4237e8072317ac6566570c291ae71078

RANDOM SEED= 533594123

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node3.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.241
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.241
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:       1023544 kB
Buffers:         42332 kB
Cached:         868940 kB
SwapCached:        268 kB
Active:         242492 kB
Inactive:       726656 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1023544 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:           14240 kB
Writeback:           0 kB
Mapped:          68004 kB
Slab:            48920 kB
Committed_AS:  1445812 kB
PageTables:       1664 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= 66518 MiB

End job on node3 on Tue Mar  6 05:08:16 UTC 2007