james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin" <robertburrelldon...@gmail.com>
Subject Re: Server's test failure and CI (Was: JAMES Server Nightly Build Report)
Date Wed, 06 Aug 2008 19:57:54 GMT
On Wed, Aug 6, 2008 at 8:34 PM, Noel J. Bergman <noel@devtech.com> wrote:
> Stefano Bagnara wrote:
>> The current process is a simple nighly build [that] is good
>> for the nighlies, but I think I don't have to explain the
>> difference between a real CI environment and a nighly build script.
> That is correct.  We have a CI at the ASF.  The nightly wasn't intended to
> replace it.  However ...
>> The specific issue I was recording in this message was the inability to
>> know what exact test failed (we have only summaries for each test class).
> The entire build log is posted to the build site.  It seems to me that if
> you want more detail, just enhance the build.  The nightly process is just a
> shell script that runs the build, generates the e-mail summary, and uploads
> the build artifacts with full log.
> Is there something you want that can't be done via the above?

think this failing test has just been getting everyone down :-/

it's been particularly irratating (it now fails about 60% of the time
for) and difficult to diagnose. it seems to be some sort of
serialization race condition but it's beyond me. don't know if you
have any ideas.

- robert

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message