1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1VUVpi-0007uc-Vo
for bitcoin-development@lists.sourceforge.net;
Fri, 11 Oct 2013 06:04:19 +0000
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;
Received: from mail-we0-f182.google.com ([74.125.82.182])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VUVpi-0007Au-4m
for bitcoin-development@lists.sourceforge.net;
Fri, 11 Oct 2013 06:04:18 +0000
Received: by mail-we0-f182.google.com with SMTP id t61so3733683wes.13
for <bitcoin-development@lists.sourceforge.net>;
Thu, 10 Oct 2013 23:04:12 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.75.165 with SMTP id d5mr15462801wjw.18.1381471451911;
Thu, 10 Oct 2013 23:04:11 -0700 (PDT)
Received: by 10.194.156.163 with HTTP; Thu, 10 Oct 2013 23:04:11 -0700 (PDT)
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
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VUVpi-0007Au-4m
Subject: [Bitcoin-development] FYI: pull-tester status
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 11 Oct 2013 06:04:19 -0000
--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'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'=
;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'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--
|
