From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] FYI: pull-tester status
Date: Fri, 11 Oct 2013 16:04:11 +1000 [thread overview]
Message-ID: <CABsx9T1y8bg9-OXZZf8KtM7c4z5p_tqPqNe1WfQeg9eKEWwE2g@mail.gmail.com> (raw)
[-- 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 --]
reply other threads:[~2013-10-11 6:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABsx9T1y8bg9-OXZZf8KtM7c4z5p_tqPqNe1WfQeg9eKEWwE2g@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.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