From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XEy2V-0005Bn-Od for bitcoin-development@lists.sourceforge.net; Wed, 06 Aug 2014 10:01:47 +0000 Received: from mail-lb0-f171.google.com ([209.85.217.171]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XEy2U-0002aX-3K for bitcoin-development@lists.sourceforge.net; Wed, 06 Aug 2014 10:01:47 +0000 Received: by mail-lb0-f171.google.com with SMTP id l4so1745058lbv.30 for ; Wed, 06 Aug 2014 03:01:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Ih5eALFihsOgvpBqNleUriVwVlSDYFS9qLM5lhN+gTw=; b=K75D/kG7iMBmgi6MdPCcaVRbZgDXXBHpvmV2O9T/Oemh568VOtYhuJ8dRZmvPP3WpD XFphGPWPCTg2eVGtEUaQr0/64Ub+BZpcbSEdVncByK2FrRkszCQ3ApuVlP/ssDXGyhPE 1KmZ/ArBZqUzA54+FKV0Ri32zqT7wADqlOpNQIi9rTNFsmEtz4zy99LxH6gePinbJuq3 CvHCSS2CDJPdOMFQA+yI1Rv3AeetlHSUf7JidekFklUQaS+R1ZLaIttFLGdQuhzQwxd/ eG4h5i4F1ns9FTwZnIzxMM5iyC0PwaVamTbYCxbYODUmyBqCapWzI/CPBartrKeIFpyJ ZjtA== X-Gm-Message-State: ALoCoQmMDM8F8PXsDhY/q45JsbeunAPXGAzLgBANNSz5j+R9RkdhwoSqcHWnnzANqKKroPP0hatJ MIME-Version: 1.0 X-Received: by 10.112.221.37 with SMTP id qb5mr9465481lbc.69.1407319299272; Wed, 06 Aug 2014 03:01:39 -0700 (PDT) Received: by 10.112.72.106 with HTTP; Wed, 6 Aug 2014 03:01:39 -0700 (PDT) X-Originating-IP: [85.53.129.68] In-Reply-To: References: Date: Wed, 6 Aug 2014 12:01:39 +0200 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: Mike Hearn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1XEy2U-0002aX-3K Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] How to create a pull tester JAR X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2014 10:01:47 -0000 Once you ave the jar, you can also build with ./configure --disable-silent-rules --disable-ccache --with-comparison-tool=3D/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 wrote: > No problem. > > The pull tester entry point can be found here: > > https://github.com/bitcoinj/bitcoinj/blob/master/core/src/test/java/com/g= oogle/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 sa= y > 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. > --=20 Jorge Tim=C3=B3n