Trace number 1807059

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_SIM 1.0UNSAT 0.214967 0.21508

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.119981
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_SIM version 1.0
0.09/0.16	This is MiniSat 2.0 beta
0.09/0.16	WARNING: for repeatability, setting FPU to use double precision
0.09/0.16	============================[ Problem Statistics ]=============================
0.09/0.16	|                                                                             |
0.09/0.16	|  Number of variables:  267                                                  |
0.09/0.16	|  Number of clauses:    12163                                                |
0.09/0.17	|  Parsing time:         0.01         s                                       |
0.09/0.17	============================[ Search Statistics ]==============================
0.09/0.17	| Conflicts |          ORIGINAL         |          LEARNT          | Progress |
0.09/0.17	|           |    Vars  Clauses Literals |    Limit  Clauses Lit/Cl |          |
0.09/0.17	===============================================================================
0.09/0.17	|         0 |     267    12163    58218 |     4054        0    nan |  0.000 % |
0.09/0.17	|       101 |     267    12163    58218 |     4459      101     11 |  0.003 % |
0.09/0.18	|       251 |     266    12163    58218 |     4905      250      9 |  0.376 % |
0.09/0.18	|       476 |     266    12163    58218 |     5396      475      9 |  0.379 % |
0.09/0.19	|       815 |     260    12163    58218 |     5935      813      8 |  2.999 % |
0.16/0.20	|      1321 |     259    12163    58218 |     6529     1318      8 |  3.379 % |
0.16/0.21	===============================================================================
0.16/0.21	restarts              : 6
0.16/0.21	conflicts             : 1549           (36029 /sec)
0.16/0.21	decisions             : 2554           (1.84 % random) (59405 /sec)
0.16/0.21	propagations          : 28984          (674156 /sec)
0.16/0.21	conflict literals     : 11371          (22.69 % deleted)
0.16/0.21	Memory used           : 2.51 MB
0.16/0.21	CPU time              : 0.042993 s
0.16/0.21	
0.16/0.21	UNSATISFIABLE
0.16/0.21	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-1807059-1242154970/watcher-1807059-1242154970 -o /tmp/evaluation-result-1807059-1242154970/solver-1807059-1242154970 -C 1200 -W 1800 -M 1800 IUT_BMB_SIM HOME/instance-1807059-1242154970.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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.00 1.00 0.99 3/65 15891
/proc/meminfo: memFree=1376376/2055920 swapFree=4180868/4192956
[pid=15891] ppid=15889 vsize=1564 CPUtime=0
/proc/15891/stat : 15891 (IUT_BMB_SIM) R 15889 15891 15271 0 -1 4194304 188 0 0 0 0 0 0 0 18 0 1 0 243527030 1601536 171 1992294400 134512640 135635349 4294956224 18446744073709551615 134533682 0 0 4096 0 0 0 0 17 0 0 0
/proc/15891/statm: 391 172 90 274 0 114 0

[startup+0.0916889 s]
/proc/loadavg: 1.00 1.00 0.99 3/65 15891
/proc/meminfo: memFree=1376376/2055920 swapFree=4180868/4192956
[pid=15891] ppid=15889 vsize=3284 CPUtime=0.08
/proc/15891/stat : 15891 (IUT_BMB_SIM) R 15889 15891 15271 0 -1 4194304 630 0 0 0 8 0 0 0 18 0 1 0 243527030 3362816 613 1992294400 134512640 135635349 4294956224 18446744073709551615 135132414 0 0 4096 0 0 0 0 17 0 0 0
/proc/15891/statm: 821 613 97 274 0 544 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 3284

[startup+0.101689 s]
/proc/loadavg: 1.00 1.00 0.99 3/65 15891
/proc/meminfo: memFree=1376376/2055920 swapFree=4180868/4192956
[pid=15891] ppid=15889 vsize=3284 CPUtime=0.09
/proc/15891/stat : 15891 (IUT_BMB_SIM) R 15889 15891 15271 0 -1 4194304 648 0 0 0 9 0 0 0 18 0 1 0 243527030 3362816 631 1992294400 134512640 135635349 4294956224 18446744073709551615 135132510 0 0 4096 0 0 0 0 17 0 0 0
/proc/15891/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.201702 s]
/proc/loadavg: 1.00 1.00 0.99 3/65 15891
/proc/meminfo: memFree=1376376/2055920 swapFree=4180868/4192956
[pid=15891] ppid=15889 vsize=3284 CPUtime=0.16
/proc/15891/stat : 15891 (IUT_BMB_SIM) S 15889 15891 15271 0 -1 4194304 654 0 0 0 12 4 0 0 18 0 1 0 243527030 3362816 636 1992294400 134512640 135635349 4294956224 18446744073709551615 135129102 0 65536 4102 0 18446744071563356171 0 0 17 0 0 0
/proc/15891/statm: 821 636 105 274 0 544 0
Current children cumulated CPU time (s) 0.16
Current children cumulated vsize (KiB) 3284

Child status: 0
Real time (s): 0.21508
CPU time (s): 0.214967
CPU user time (s): 0.168974
CPU system time (s): 0.045993
CPU usage (%): 99.9474
Max. virtual memory (cumulated for all children) (KiB): 3284

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.168974
system time used= 0.045993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1676
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= 5
involuntary context switches= 31

runsolver used 0.000999 second user time and 0.007998 second system time

The end

Launcher Data

Begin job on node79 at 2009-05-12 21:02:50
IDJOB=1807059
IDBENCH=71149
IDSOLVER=650
FILE ID=node79/1807059-1242154970
PBS_JOBID= 9289647
Free space on /tmp= 66232 MiB

SOLVER NAME= IUT_BMB_SIM 1.0
BENCH NAME= SAT09/CRAFTED/modcircuits/owp_4vars_5gates.cnf
COMMAND LINE= IUT_BMB_SIM BENCHNAME TMPDIR
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1807059-1242154970/watcher-1807059-1242154970 -o /tmp/evaluation-result-1807059-1242154970/solver-1807059-1242154970 -C 1200 -W 1800 -M 1800  IUT_BMB_SIM HOME/instance-1807059-1242154970.cnf HOME

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

MD5SUM BENCH= fe245e5f46bcc987fd412946151b9c92
RANDOM SEED=1532996694

node79.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.220
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.220
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1376920 kB
Buffers:         64092 kB
Cached:         529396 kB
SwapCached:       7224 kB
Active:          69784 kB
Inactive:       533336 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1376920 kB
SwapTotal:     4192956 kB
SwapFree:      4180868 kB
Dirty:            3008 kB
Writeback:           0 kB
Mapped:          14192 kB
Slab:            61964 kB
Committed_AS:   869504 kB
PageTables:       1384 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= 66228 MiB
End job on node79 at 2009-05-12 21:02:51