Trace number 338068

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.046992 0.049011

General information on the benchmark

Namecrafted/Difficult/contest05/QG/
QG6-gensys-ukn003.sat05-2726.reshuffled-07.cnf
MD5SUM92c8b4fc23a7c22313979a2d9b3b5a58
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark224.011
Satisfiable
(Un)Satisfiability was proved
Number of variables1691
Number of clauses9177
Sum of the clauses size77698
Maximum clause length16
Minimum clause length1
Number of clauses of size 133
Number of clauses of size 2289
Number of clauses of size 31389
Number of clauses of size 4171
Number of clauses of size 5960
Number of clauses of size over 56335

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:  2123                                                 |
0.00/0.00	|  Number of clauses:    9177                                                 |
0.00/0.04	|  Parsing time:         0.04         s                                       |
0.00/0.04	Solved by unit propagation
0.00/0.04	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/node7/watcher-338068-1173679814 -o ROOT/results/node7/solver-338068-1173679814 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/338068-1173679814/minimarch /tmp/evaluation/338068-1173679814/instance-338068-1173679814.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.99 0.98 0.99 3/77 7609
/proc/meminfo: memFree=1619984/2055920 swapFree=4147416/4192956
[pid=7609] ppid=7607 vsize=2000 CPUtime=0
/proc/7609/stat : 7609 (minimarch) R 7607 7609 6468 0 -1 4194304 264 0 0 0 0 0 0 0 18 0 1 0 387936091 2048000 248 18446744073709551615 134512640 135054332 4294956720 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/7609/statm: 500 249 51 132 0 365 0

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

Child status: 20
Real time (s): 0.049011
CPU time (s): 0.046992
CPU user time (s): 0.044993
CPU system time (s): 0.001999
CPU usage (%): 95.8805
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node7 on Mon Mar 12 06:10:14 UTC 2007

IDJOB= 338068
IDBENCH= 24714
IDSOLVER= 110
FILE ID= node7/338068-1173679814

PBS_JOBID= 4101475

Free space on /tmp= 66483 MiB

SOLVER NAME= minimarch 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/crafted/Difficult/contest05/QG/QG6-gensys-ukn003.sat05-2726.reshuffled-07.cnf
COMMAND LINE= /tmp/evaluation/338068-1173679814/minimarch /tmp/evaluation/338068-1173679814/instance-338068-1173679814.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node7/watcher-338068-1173679814 -o ROOT/results/node7/solver-338068-1173679814 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/338068-1173679814/minimarch /tmp/evaluation/338068-1173679814/instance-338068-1173679814.cnf            

META MD5SUM SOLVER= cd0143c15836d32fe9acb8d523a59b67
MD5SUM BENCH=  92c8b4fc23a7c22313979a2d9b3b5a58

RANDOM SEED= 802701134

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node7.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:      2055920 kB
MemFree:       1620392 kB
Buffers:         41252 kB
Cached:         302564 kB
SwapCached:       8628 kB
Active:         216276 kB
Inactive:       150508 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1620392 kB
SwapTotal:     4192956 kB
SwapFree:      4147416 kB
Dirty:            2796 kB
Writeback:           0 kB
Mapped:          29952 kB
Slab:            54256 kB
Committed_AS:  1310648 kB
PageTables:       1764 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= 66483 MiB

End job on node7 on Mon Mar 12 06:10:14 UTC 2007