Trace number 1594730

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
SAT07 reference solver: minisat SAT 2007UNSAT 0.245961 0.246629

General information on the benchmark

NameCRAFTED/modcircuits/
owp_4vars_5gates.cnf
MD5SUMfe245e5f46bcc987fd412946151b9c92
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.06099
Satisfiable
(Un)Satisfiability was proved
Number of variables267
Number of clauses23747
Sum of the clauses size136362
Maximum clause length19
Minimum clause length1
Number of clauses of size 164
Number of clauses of size 2700
Number of clauses of size 31
Number of clauses of size 4563
Number of clauses of size 51926
Number of clauses of size over 520493

Solver Data 

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:  267                                                  |
0.00/0.00	c |  Number of clauses:    23747                                                |
0.00/0.03	c |  Parsing time:         0.03         s                                       |
0.09/0.16	c ============================[ Search Statistics ]==============================
0.09/0.16	c | Conflicts |          ORIGINAL         |          LEARNT          | Progress |
0.09/0.16	c |           |    Vars  Clauses Literals |    Limit  Clauses Lit/Cl |          |
0.09/0.16	c ===============================================================================
0.09/0.16	c |         0 |     155     5370    26813 |     1790        0    nan |  0.000 % |
0.09/0.16	c |       101 |     155     5370    26813 |     1969      101     12 | 25.471 % |
0.09/0.16	c |       251 |     154     5370    26813 |     2165      250     11 | 25.848 % |
0.09/0.17	c |       476 |     154     5370    26813 |     2382      473     10 | 26.595 % |
0.09/0.18	c |       814 |     152     5370    26813 |     2620      809     10 | 27.342 % |
0.19/0.20	c |      1321 |     149     5370    26813 |     2882     1315     10 | 27.717 % |
0.19/0.22	c |      2080 |     149     5370    26813 |     3171     2074      9 | 27.721 % |
0.19/0.24	c ===============================================================================
0.19/0.24	c restarts              : 7
0.19/0.24	c conflicts             : 2623           (10752 /sec)
0.19/0.24	c decisions             : 3968           (1.64 % random) (16265 /sec)
0.19/0.24	c propagations          : 58373          (239271 /sec)
0.19/0.24	c conflict literals     : 22736          (18.06 % deleted)
0.19/0.24	c Memory used           : 3.62 MB
0.19/0.24	c CPU time              : 0.243962 s
0.19/0.24	c 
0.19/0.24	s UNSATISFIABLE

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1594730-1239279470/watcher-1594730-1239279470 -o /tmp/evaluation-result-1594730-1239279470/solver-1594730-1239279470 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/minisat_noassertions HOME/instance-1594730-1239279470.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): 1800 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.15 0.03 0.01 3/64 14414
/proc/meminfo: memFree=1357720/2055920 swapFree=4177948/4192956
[pid=14414] ppid=14412 vsize=1856 CPUtime=0
/proc/14414/stat : 14414 (minisat_noasser) R 14412 14414 14350 0 -1 4194304 288 0 0 0 0 0 0 0 18 0 1 0 1200613332 1900544 274 1992294400 134512640 135048876 4294956224 18446744073709551615 134686936 0 0 4096 3 0 0 0 17 1 0 0
/proc/14414/statm: 464 274 50 130 0 331 0

[startup+0.0559399 s]
/proc/loadavg: 0.15 0.03 0.01 3/64 14414
/proc/meminfo: memFree=1357720/2055920 swapFree=4177948/4192956
[pid=14414] ppid=14412 vsize=3700 CPUtime=0.05
/proc/14414/stat : 14414 (minisat_noasser) R 14412 14414 14350 0 -1 4194304 751 0 0 0 5 0 0 0 18 0 1 0 1200613332 3788800 737 1992294400 134512640 135048876 4294956224 18446744073709551615 134546101 0 0 4096 3 0 0 0 17 1 0 0
/proc/14414/statm: 925 737 62 130 0 792 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 3700

[startup+0.101949 s]
/proc/loadavg: 0.15 0.03 0.01 3/64 14414
/proc/meminfo: memFree=1357720/2055920 swapFree=4177948/4192956
[pid=14414] ppid=14412 vsize=3700 CPUtime=0.09
/proc/14414/stat : 14414 (minisat_noasser) R 14412 14414 14350 0 -1 4194304 753 0 0 0 9 0 0 0 18 0 1 0 1200613332 3788800 739 1992294400 134512640 135048876 4294956224 18446744073709551615 134525607 0 0 4096 3 0 0 0 17 1 0 0
/proc/14414/statm: 925 739 62 130 0 792 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3700

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

[startup+0.201971 s]
/proc/loadavg: 0.15 0.03 0.01 3/64 14414
/proc/meminfo: memFree=1357720/2055920 swapFree=4177948/4192956
[pid=14414] ppid=14412 vsize=3700 CPUtime=0.19
/proc/14414/stat : 14414 (minisat_noasser) R 14412 14414 14350 0 -1 4194304 805 0 0 0 19 0 0 0 18 0 1 0 1200613332 3788800 747 1992294400 134512640 135048876 4294956224 18446744073709551615 134548110 0 0 4096 3 0 0 0 17 1 0 0
/proc/14414/statm: 925 747 66 130 0 792 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 3700

Child status: 20
Real time (s): 0.246629
CPU time (s): 0.245961
CPU user time (s): 0.243962
CPU system time (s): 0.001999
CPU usage (%): 99.7291
Max. virtual memory (cumulated for all children) (KiB): 3700

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.243962
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= 811
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= 2
involuntary context switches= 0

runsolver used 0.002999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node10 at 2009-04-09 14:17:50
IDJOB=1594730
IDBENCH=71149
IDSOLVER=556
FILE ID=node10/1594730-1239279470
PBS_JOBID= 9115472
Free space on /tmp= 65404 MiB

SOLVER NAME= SAT07 reference solver: minisat SAT 2007
BENCH NAME= SAT09/CRAFTED/modcircuits/owp_4vars_5gates.cnf
COMMAND LINE= HOME/minisat_noassertions BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1594730-1239279470/watcher-1594730-1239279470 -o /tmp/evaluation-result-1594730-1239279470/solver-1594730-1239279470 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/minisat_noassertions HOME/instance-1594730-1239279470.cnf

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= fe245e5f46bcc987fd412946151b9c92
RANDOM SEED=333840869

node10.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.272
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.272
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:       1358136 kB
Buffers:         46344 kB
Cached:         575160 kB
SwapCached:       8856 kB
Active:          36072 kB
Inactive:       596380 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1358136 kB
SwapTotal:     4192956 kB
SwapFree:      4177948 kB
Dirty:            2156 kB
Writeback:           0 kB
Mapped:          16624 kB
Slab:            51336 kB
Committed_AS:  3393132 kB
PageTables:       1380 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= 65404 MiB
End job on node10 at 2009-04-09 14:17:51