From: "Jorge Timón" <jtimon@monetize•io>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] How to create a pull tester JAR
Date: Wed, 6 Aug 2014 12:01:39 +0200 [thread overview]
Message-ID: <CAC1+kJNy=AeVk4=SJ3Zc=yq0ayjTcfT3pKPfFfKjQpmqoBNHcw@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2n9uRxbpyvF8D0478umbJ-K_sz9V8ahz5EXaCQRaM8sw@mail.gmail.com>
Once you ave the jar, you can also build with
./configure --disable-silent-rules --disable-ccache
--with-comparison-tool=/path/to/your/BitcoindComparisonTool.jar
Instead of the regular
./configure
And after that "make check" will run most of the tests the pull tester does.
On 8/5/14, Mike Hearn <mike@plan99•net> wrote:
> No problem.
>
> The pull tester entry point can be found here:
>
> https://github.com/bitcoinj/bitcoinj/blob/master/core/src/test/java/com/google/bitcoin/core/BitcoindComparisonTool.java
>
> (nb: in the near future I will be re-namespacing the library from
> com.google.bitcoin to org.bitcoinj to reflect that it no longer has
> anything to do with Google and then this link will break).
>
> The code itself is a rather bad example of copy/paste coding and I can say
> that, because Matt knows it and already plans to refactor things ;) So if
> anyone is thinking of adding tests to the framework coordinate with him
> first to ensure you don't end up conflicting with a big refactor/rewrite.
>
--
Jorge Timón
prev parent reply other threads:[~2014-08-06 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 15:00 Mike Hearn
2014-08-05 15:11 ` Mike Hearn
2014-08-05 16:11 ` Andreas Schildbach
2014-08-05 15:45 ` Jeff Garzik
2014-08-05 16:58 ` Mike Hearn
2014-08-06 10:01 ` Jorge Timón [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='CAC1+kJNy=AeVk4=SJ3Zc=yq0ayjTcfT3pKPfFfKjQpmqoBNHcw@mail.gmail.com' \
--to=jtimon@monetize$(echo .)io \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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