public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Angel Leon <gubatron@gmail•com>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [QT] how to disable block verification for faster UI testing?
Date: Wed, 19 Mar 2014 14:36:31 -0400	[thread overview]
Message-ID: <CADZB0_byfS8_8qZ+w-GGBzFYCdeD+v+YGWVVg5dx5bRcxWHZWg@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJDZGS5Mm-hcZ8r6OevEGvULH67HOG99TeCRX7cMoeyf7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]

"If you have database problems are you perhaps switching between 0.8.x and
0.9.x with the same directory?"
I think that may have been the issue.

Maybe now that I have a 0.9.0 official binary, when I switch to the source
builds I won't have the issue.

However, I think I'll do what you do and have separate bitcoin data
directories, that's probably the best.

not trying to test anything specifically, just codign, building, launching
over and over, would like to make the startup of the Qt client faster.

http://twitter.com/gubatron


On Wed, Mar 19, 2014 at 2:22 PM, Wladimir <laanwj@gmail•com> wrote:

>
> On Wed, Mar 19, 2014 at 6:27 PM, Angel Leon <gubatron@gmail•com> wrote:
>
>> the command line options mention a -checklevel  parameter.
>> I've been passing 0 assuming there'd be little to no verification, but
>> it's happened a few times that when I open the official binary (while not
>> doing development) there's some sort of database corruption and Bitcoin-Qt
>> needs to reindex blocks on disk, a process that can take probably a whole
>> day.
>>
>> how do you guys develop the UI and avoid these issues?
>>
>
> In general I do very little with the database while developing the UI. I
> have various seperate bitcoin data directories (both testnet and mainnet)
> to try things out. Before doing something risky I just make a copy.
>
> These days I also do a lot of development with -regtest, as it allows
> quickly setting up test scenarios.
>
> What are you trying to test specifically? The progress bar while
> reindexing?
>
> If you have database problems are you perhaps switching between 0.8.x and
> 0.9.x with the same directory? In that case see the downgrading warning
> here: https://bitcoin.org/bin/0.9.0/README.txt .
>
> Wladimir
>
>

[-- Attachment #2: Type: text/html, Size: 2937 bytes --]

      reply	other threads:[~2014-03-19 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 17:27 Angel Leon
2014-03-19 18:22 ` Wladimir
2014-03-19 18:36   ` Angel Leon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADZB0_byfS8_8qZ+w-GGBzFYCdeD+v+YGWVVg5dx5bRcxWHZWg@mail.gmail.com \
    --to=gubatron@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=laanwj@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox