RemoteDelivery test issue (Was: Server's test failure and CI)

[Stefano Bagnara <ap...@bago.org>]

Robert Burrell Donkin ha scritto:
> On Thu, Aug 7, 2008 at 10:54 AM, Stefano Bagnara <ap...@bago.org> wrote:
>> Robert Burrell Donkin ha scritto:
>>> On Wed, Aug 6, 2008 at 8:34 PM, Noel J. Bergman <no...@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.
>> If we agree this probably is an issue in JVM/classpath but we don't have
>> time dealing with SUN for this IMHO we can even add a comment to that test..
>> e.g: catch the assert failure and add a comment about this whole thing.
> 
> if this is a JVM issue then couldn't we just narrow down the known bad versions?
> 
> - robert

I think we saw it on every platform running very often the tests.

Even if it only happened once in my environment it did. I also saw it on 
hudson, and you saw it.

AFAIKT it could even be a non fixed issue existing in every Sun jvm. 
Trying IBM/BEA/ASF JVM could give some more answers (I don't know what 
we can conclude if they don't give the issue, only what we can guess if 
they give the same issue).

Stefano

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