Trace number 1733864

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
IUT_BMB_SAT 1.0UNSAT 0.286955 0.28631

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 IUT_BMB_SAT version 1.0
0.09/0.17	c WARNING: for repeatability, setting FPU to use double precision
0.09/0.17	c ============================[ Problem Statistics ]=============================
0.09/0.17	c |                                                                             |
0.09/0.17	c |  Number of variables:  267                                                  |
0.09/0.17	c |  Number of clauses:    12163                                                |
0.09/0.18	c |  Parsing time:         0.01         s                                       |
0.15/0.24	c ============================[ Search Statistics ]==============================
0.15/0.24	c | Conflicts |          ORIGINAL         |          LEARNT          | Progress |
0.15/0.24	c |           |    Vars  Clauses Literals |    Limit  Clauses Lit/Cl |          |
0.15/0.24	c ===============================================================================
0.15/0.24	c |         0 |     155     5370    26813 |     1790        0    nan |  0.000 % |
0.15/0.24	c |       100 |     155     5370    26813 |     1969      100     10 |  1.501 % |
0.15/0.24	c |       250 |     155     5370    26813 |     2165      250      9 |  1.500 % |
0.15/0.25	c |       475 |     155     5370    26813 |     2382      475      8 |  1.502 % |
0.15/0.26	c |       812 |     154     5370    26813 |     2620      811      9 |  1.874 % |
0.15/0.27	c |      1319 |     149     5370    26813 |     2882     1314      8 |  3.747 % |
0.15/0.28	c ===============================================================================
0.15/0.28	c restarts              : 6
0.15/0.28	c conflicts             : 1455           (13351 /sec)
0.15/0.28	c decisions             : 2008           (1.79 % random) (18425 /sec)
0.15/0.28	c propagations          : 30318          (278190 /sec)
0.15/0.28	c conflict literals     : 11605          (22.80 % deleted)
0.15/0.28	c Memory used           : 2.89 MB
0.15/0.28	c CPU time              : 0.108983 s
0.15/0.28	
0.15/0.28	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-1733864-1240793269/watcher-1733864-1240793269 -o /tmp/evaluation-result-1733864-1240793269/solver-1733864-1240793269 -C 1200 -W 1800 -M 1800 --output-limit 1,15 IUT_BMB_SAT HOME/instance-1733864-1240793269.cnf HOME 

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.91 0.97 0.99 3/64 507
/proc/meminfo: memFree=1801344/2055924 swapFree=4180788/4192956
[pid=507] ppid=505 vsize=1564 CPUtime=0
/proc/507/stat : 507 (IUT_BMB_SAT) R 505 507 470 0 -1 4194304 189 0 0 0 0 0 0 0 18 0 1 0 107361302 1601536 172 1992294400 134512640 135635285 4294956224 18446744073709551615 134533654 0 0 4096 0 0 0 0 17 0 0 0
/proc/507/statm: 391 173 90 274 0 114 0

[startup+0.0742699 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 507
/proc/meminfo: memFree=1801344/2055924 swapFree=4180788/4192956
[pid=507] ppid=505 vsize=2888 CPUtime=0.07
/proc/507/stat : 507 (IUT_BMB_SAT) R 505 507 470 0 -1 4194304 556 0 0 0 7 0 0 0 18 0 1 0 107361302 2957312 539 1992294400 134512640 135635285 4294956224 18446744073709551615 135072790 0 0 4096 0 0 0 0 17 0 0 0
/proc/507/statm: 722 539 97 274 0 445 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 2888

[startup+0.101275 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 507
/proc/meminfo: memFree=1801344/2055924 swapFree=4180788/4192956
[pid=507] ppid=505 vsize=3284 CPUtime=0.09
/proc/507/stat : 507 (IUT_BMB_SAT) R 505 507 470 0 -1 4194304 648 0 0 0 9 0 0 0 18 0 1 0 107361302 3362816 631 1992294400 134512640 135635285 4294956224 18446744073709551615 135132478 0 0 4096 0 0 0 0 17 0 0 0
/proc/507/statm: 821 631 100 274 0 544 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3284

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

[startup+0.201296 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 507
/proc/meminfo: memFree=1801344/2055924 swapFree=4180788/4192956
[pid=507] ppid=505 vsize=3284 CPUtime=0.15
/proc/507/stat : 507 (IUT_BMB_SAT) S 505 507 470 0 -1 4194304 654 0 0 0 11 4 0 0 18 0 1 0 107361302 3362816 636 1992294400 134512640 135635285 4294956224 18446744073709551615 135129070 0 65536 4102 0 18446744071563356171 0 0 17 0 0 0
/proc/507/statm: 821 636 105 274 0 544 0
Current children cumulated CPU time (s) 0.15
Current children cumulated vsize (KiB) 3284

Child status: 0
Real time (s): 0.28631
CPU time (s): 0.286955
CPU user time (s): 0.231964
CPU system time (s): 0.054991
CPU usage (%): 100.225
Max. virtual memory (cumulated for all children) (KiB): 3284

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

runsolver used 0.001999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node6 at 2009-04-27 02:47:49
IDJOB=1733864
IDBENCH=71149
IDSOLVER=523
FILE ID=node6/1733864-1240793269
PBS_JOBID= 9187368
Free space on /tmp= 66336 MiB

SOLVER NAME= IUT_BMB_SAT 1.0
BENCH NAME= SAT09/CRAFTED/modcircuits/owp_4vars_5gates.cnf
COMMAND LINE= IUT_BMB_SAT BENCHNAME TMPDIR
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1733864-1240793269/watcher-1733864-1240793269 -o /tmp/evaluation-result-1733864-1240793269/solver-1733864-1240793269 -C 1200 -W 1800 -M 1800 --output-limit 1,15  IUT_BMB_SAT HOME/instance-1733864-1240793269.cnf HOME

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

MD5SUM BENCH= fe245e5f46bcc987fd412946151b9c92
RANDOM SEED=1788276056

node6.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.281
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.281
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:      2055924 kB
MemFree:       1801824 kB
Buffers:         33412 kB
Cached:         151368 kB
SwapCached:       6028 kB
Active:          72240 kB
Inactive:       120824 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1801824 kB
SwapTotal:     4192956 kB
SwapFree:      4180788 kB
Dirty:            3016 kB
Writeback:           0 kB
Mapped:          13972 kB
Slab:            47060 kB
Committed_AS:   488724 kB
PageTables:       1452 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= 66332 MiB
End job on node6 at 2009-04-27 02:47:50