* [Bitcoin-development] FYI: pull-tester status
@ 2013-10-11 6:04 Gavin Andresen
0 siblings, 0 replies; only message in thread
From: Gavin Andresen @ 2013-10-11 6:04 UTC (permalink / raw)
To: Bitcoin Dev
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1567 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-10-11 6:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-10-11 6:04 [Bitcoin-development] FYI: pull-tester status Gavin Andresen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox