It's not related to your commit. It's a known issue:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=14392
and it's happening more often in recent builds. Byron is currently
investigating. I will raise the priority of this bug.
Jane
On 11/8/10 9:55 AM, Sanjeeb Sahoo wrote:
> On Monday 08 November 2010 11:00 PM, Ed Burns wrote:
>>>>>>> On Mon, 08 Nov 2010 08:59:41 -0800, Ed Burns<ed.burns_at_sun.com>
>>>>>>> said:
>> SS> If the test passes, you can go ahead with the integration.
>>
>> EB> Thank you so much, I really appreciate your consideration in
>> giving the
>> EB> conditional approval so I don't have to wait for another round
>> of email
>> EB> exchange.
>>
>> EB> Committed revision 42566.
>>
>> I checked hudson after committing to see that build 6731, from revision
>> 42565, failed.
>>
>> test.clusterteardown.ClusterTeardownTest.deleteInstanceTest
>>
>> The next build, 6732 [1], does include my commit and is still running
>> but it's likely that the same failure will occur. Since the failure
>> occured prior to my commit, it is not related to my commit.
>> Nonetheless, I can back out my commit if it would help to resolve the
>> failure.
>>
>> Please advise.
>>
> That test is failing for a number of builds now and the root cause is
> not identified. It is definitely not caused by your change, so no need
> to revert your change at this point of time.
>
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>