Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.182 as permitted sender)
	client-ip=74.125.82.182; envelope-from=gavinandresen@gmail.com;
	helo=mail-we0-f182.google.com; 
MIME-Version: 1.0
Date: Fri, 11 Oct 2013 16:04:11 +1000
Message-ID: <CABsx9T1y8bg9-OXZZf8KtM7c4z5p_tqPqNe1WfQeg9eKEWwE2g@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7bb04bc2289d0e04e870e312
Subject: [Bitcoin-development] FYI: pull-tester status
Precedence: list

--047d7bb04bc2289d0e04e870e312
Content-Type: text/plain; charset=ISO-8859-1

Since the autotools merge, the pull-tester has been misbehaving-- marking
valid pulls as invalid, etc.

So I've turned off some pull-tester features until somebody has time to
figure out how to fix them. Right now, pull-tester does the following:

+ Cross-compile windows binaries
+ Compile linux binaries
+ Run unit tests (binaries compiled on linux)

The following features are turned off:

- Running unit tests under wine with cross-compiled windows binaries
- Running the block-chain-compatibility tester
- Computing code coverage

Medium-term, there are several changes that need to be made to the
pull-tester environment; I'd like the following to get done:

+ Upgrade the pull-tester machine from Ubuntu 10.04 to 12.04. Or, probably
better, create a new 12.04 virtual machine and move the pull-tester over to
it.

+ Upgrade compilers/dependencies based on what we think we'll use for the
0.9 release.

+ Figure out how to unify the pull-tester and gitian build processes.
 Maybe the pull-tester should run gitian builds to create binaries (that
are then tested against the blockchain tester)? Maybe the pull-tester
scripts should be gitian scripts, which the pull-tester machine runs inside
an LXC container?

-- 
--
Gavin Andresen

--047d7bb04bc2289d0e04e870e312
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Since the autotools merge, the pull-tester has been misbeh=
aving-- marking valid pulls as invalid, etc.<div><br></div><div>So I&#39;ve=
 turned off some pull-tester features until somebody has time to figure out=
 how to fix them. Right now, pull-tester does the following:</div>
<div><br></div><div>+ Cross-compile windows binaries</div><div>+ Compile li=
nux binaries</div><div>+ Run unit tests (binaries compiled on linux)</div><=
div><br></div><div>The following features are turned off:</div><div><br>
</div><div>- Running unit tests under wine with cross-compiled windows bina=
ries</div><div>- Running the block-chain-compatibility tester</div><div>- C=
omputing code coverage</div><div><div><br></div><div>Medium-term, there are=
 several changes that need to be made to the pull-tester environment; I&#39=
;d like the following to get done:</div>
<div><br></div><div>+ Upgrade the pull-tester machine from Ubuntu 10.04 to =
12.04. Or, probably better, create a new 12.04 virtual machine and move the=
 pull-tester over to it.</div><div><br></div><div>+ Upgrade compilers/depen=
dencies based on what we think we&#39;ll use for the 0.9 release.</div>
<div><br></div><div>+ Figure out how to unify the pull-tester and gitian bu=
ild processes. =A0Maybe the pull-tester should run gitian builds to create =
binaries (that are then tested against the blockchain tester)? Maybe the pu=
ll-tester scripts should be gitian scripts, which the pull-tester machine r=
uns inside an LXC container?<br clear=3D"all">
<div><br></div>-- <br>--<br>Gavin Andresen<br>
</div></div></div>

--047d7bb04bc2289d0e04e870e312--