Scott Zhong wrote:
For 4.3.x and trunk, I can rerun selected runs if it is an
infrastructure issue that caused the failure.
I was hoping for some sort of automation.
I have a pending merge from 4.2.x to 4.3.x that I'd like to
commit today. Since 4.3.x is scheduled for a full set of
builds on the 16th (today) let's see how that goes first.
Trunk doesn't look too bad so we can probably leave it as
is this time. I also plan to merge 4.2.x to trunk so we'll
see how that does early next month.
Martin
-----Original Message-----
From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of Martin Sebor
Sent: Thursday, May 15, 2008 2:47 PM
To: [email protected]
Subject: Re: nightly build errors 5/15
Scott Zhong wrote:
gcc 4.3.0 build errors -- working on fixing.
Windows xp -- infrastructure machine error (fixed).
Aix 5.3 -- error in building lib, this was mentioned earlier.
On 4.2.x, there are also some errors on FreeBSD (5/13) and HP-UX
11.23 (5/7), although more recent builds are passing. I assume
the errors have been resolved?
http://stdcxx.apache.org/builds/4.2.x/logs/
On 4.3.x, we also have errors on FreeBSD and Vista, in addition
to XP and AIX:
http://stdcxx.apache.org/builds/4.3.x/logs/
Trunk looks the best, but even there we have a few errors on XP:
http://stdcxx.apache.org/builds/trunk/logs/
This raises the question: since both 4.3.x and trunk are set up
to build only infrequently, failures like this can easily ruin
two weeks or even a month worth of test results. Can something
be done to "fix" these errors without re-running the full set
of builds?
Martin
