Trace number 1806898

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.0SAT 0.218966 0.221242

General information on the benchmark

NameCRAFTED/ramseycube/
Q3inK09.cnf
MD5SUM167bdfed21466d25646b3f9481920143
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.021995
Satisfiable
(Un)Satisfiability was proved
Number of variables36
Number of clauses15120
Sum of the clauses size181440
Maximum clause length12
Minimum clause length12
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 30
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 515120

Solver Data 

0.00/0.00	c IUT_BMB_SIM version 1.0
0.09/0.19	This is MiniSat 2.0 beta
0.09/0.19	WARNING: for repeatability, setting FPU to use double precision
0.09/0.19	============================[ Problem Statistics ]=============================
0.09/0.19	|                                                                             |
0.09/0.19	|  Number of variables:  36                                                   |
0.09/0.19	|  Number of clauses:    15120                                                |
0.18/0.21	|  Parsing time:         0.02         s                                       |
0.18/0.21	============================[ Search Statistics ]==============================
0.18/0.21	| Conflicts |          ORIGINAL         |          LEARNT          | Progress |
0.18/0.21	|           |    Vars  Clauses Literals |    Limit  Clauses Lit/Cl |          |
0.18/0.21	===============================================================================
0.18/0.21	|         0 |      36    15120   181440 |     5040        0    nan |  0.000 % |
0.18/0.21	===============================================================================
0.18/0.21	restarts              : 1
0.18/0.21	conflicts             : 0              (0 /sec)
0.18/0.21	decisions             : 27             (0.00 % random) (1500 /sec)
0.18/0.21	propagations          : 36             (2000 /sec)
0.18/0.21	conflict literals     : 0              ( nan % deleted)
0.18/0.21	Memory used           : 3.01 MB
0.18/0.21	CPU time              : 0.017997 s
0.18/0.21	
0.18/0.21	SATISFIABLE
0.18/0.21	s SATISFIABLE
0.18/0.21	v -1 2 3 4 5 6 -7 -8 9 10 11 12 13 -14 -15 -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 -29 -30 -31 -32 -33 -34 -35 -36 0

Verifier Data 

OK

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1806898-1242153396/watcher-1806898-1242153396 -o /tmp/evaluation-result-1806898-1242153396/solver-1806898-1242153396 -C 1200 -W 1800 -M 1800 IUT_BMB_SIM HOME/instance-1806898-1242153396.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: 0.99 0.97 0.91 3/64 19065
/proc/meminfo: memFree=986232/2055924 swapFree=4180096/4192956
[pid=19065] ppid=19063 vsize=1464 CPUtime=0
/proc/19065/stat : 19065 (IUT_BMB_SIM) R 19063 19065 18624 0 -1 4194304 194 0 0 0 0 0 0 0 18 0 1 0 243373952 1499136 177 1992294400 134512640 135635349 4294956224 18446744073709551615 135072822 0 0 4096 0 0 0 0 17 0 0 0
/proc/19065/statm: 366 177 95 274 0 89 0

[startup+0.0680691 s]
/proc/loadavg: 0.99 0.97 0.91 3/64 19065
/proc/meminfo: memFree=986232/2055924 swapFree=4180096/4192956
[pid=19065] ppid=19063 vsize=3208 CPUtime=0.06
/proc/19065/stat : 19065 (IUT_BMB_SIM) R 19063 19065 18624 0 -1 4194304 592 0 0 0 6 0 0 0 18 0 1 0 243373952 3284992 575 1992294400 134512640 135635349 4294956224 18446744073709551615 134621877 0 0 4096 0 0 0 0 17 0 0 0
/proc/19065/statm: 802 575 95 274 0 525 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 3208

[startup+0.101075 s]
/proc/loadavg: 0.99 0.97 0.91 3/64 19065
/proc/meminfo: memFree=986232/2055924 swapFree=4180096/4192956
[pid=19065] ppid=19063 vsize=3636 CPUtime=0.09
/proc/19065/stat : 19065 (IUT_BMB_SIM) R 19063 19065 18624 0 -1 4194304 727 0 0 0 8 1 0 0 18 0 1 0 243373952 3723264 710 1992294400 134512640 135635349 4294956224 18446744073709551615 135132510 0 0 4096 0 0 0 0 17 0 0 0
/proc/19065/statm: 909 710 98 274 0 632 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3636

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

[startup+0.201099 s]
/proc/loadavg: 0.99 0.97 0.91 3/64 19065
/proc/meminfo: memFree=986232/2055924 swapFree=4180096/4192956
[pid=19065] ppid=19063 vsize=3636 CPUtime=0.18
/proc/19065/stat : 19065 (IUT_BMB_SIM) S 19063 19065 18624 0 -1 4194304 734 0 0 0 12 6 0 0 18 0 1 0 243373952 3723264 716 1992294400 134512640 135635349 4294956224 18446744073709551615 135129102 0 65536 4102 0 18446744071563356171 0 0 17 0 0 0
/proc/19065/statm: 909 716 104 274 0 632 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 3636

Child status: 0
Real time (s): 0.221242
CPU time (s): 0.218966
CPU user time (s): 0.148977
CPU system time (s): 0.069989
CPU usage (%): 98.9712
Max. virtual memory (cumulated for all children) (KiB): 3636

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.148977
system time used= 0.069989
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1893
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= 6
involuntary context switches= 24

runsolver used 0.002999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node6 at 2009-05-12 20:36:36
IDJOB=1806898
IDBENCH=71125
IDSOLVER=650
FILE ID=node6/1806898-1242153396
PBS_JOBID= 9289715
Free space on /tmp= 66228 MiB

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

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

MD5SUM BENCH= 167bdfed21466d25646b3f9481920143
RANDOM SEED=50448750

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:        986712 kB
Buffers:         78384 kB
Cached:         891180 kB
SwapCached:       6644 kB
Active:         103916 kB
Inactive:       874004 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:        986712 kB
SwapTotal:     4192956 kB
SwapFree:      4180096 kB
Dirty:            2768 kB
Writeback:           0 kB
Mapped:          14008 kB
Slab:            77316 kB
Committed_AS:   967936 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= 66228 MiB
End job on node6 at 2009-05-12 20:36:36