dev@glassfish.java.net

Re: Hudson QL job failing for last 17 hours

From: Lloyd Chambers <Lloyd.Chambers_at_Sun.COM>
Date: Tue, 09 Sep 2008 10:36:39 -0700

IMO, all test jobs should run on a MINIMUM of 4 cores, 8 or 16 would
be a far more realistic match for what customers would use today.


On Sep 9, 2008, at 10:35 AM, Sahoo wrote:

> First, there are a couple of QL jobs: v3-quicklook, v3-dev-builds-
> quicklook. Which job was changed to run on dual core? The jobs I was
> referring is v3-dev-builds-quicklook and I see it has been running
> on same system called jennings for last 3 days. Amy also referred to
> same job.
>
> The other QL job has also started to fail around the same checkin.
> Look at http://hudson.sfbay/job/glassfish-v3/7710/. Scroll down and
> you shall see the downstream QL job failed for this buid.
>
> Thanks
> Sahoo
>
> Amy Roh wrote:
>> Looks like there is a big gap between the last success 3:08 and
>> unstable 3:59 which might have been due to the Hudson build moved
>> to a new machine.
>>
>> Unstable #1742 Sep 8, 2008 4:14:55 PM
>> Unstable #1741 Sep 8, 2008 3:59:44 PM
>> Success #1740 Sep 8, 2008 3:08:12 PM
>> Success #1739 Sep 8, 2008 2:59:06 PM
>>
>> If the Hudson build was moved to produce the failures then we
>> cannot rely on the Hudson until the failures have been resolved.
>>
>> Amy
>>
>> Carla Mott wrote:
>>> There is a failure in the QL tests that only some of us are
>>> seeing. We all are running on dual core machines and the failure
>>> seems to be due to a race condition. JeanFrancois is looking into
>>> that bug now.
>>>
>>> The Hudson build was moved to a machine that would reproduce the
>>> bug so in the future we would catch it as early as possible.
>>>
>>> Carla
>>>
>>> Amy Roh wrote:
>>>> I ran QL for 22477 and it passed for me. It still passes for me.
>>>> Let me try with a clean workspace.
>>>>
>>>> I thought we get an email notification if a commit breaks QL.
>>>> Apologies if it indeed was 22477 that broke QL.
>>>>
>>>> On Sep 9, 2008, at 8:12 AM, Sahoo <Sahoo_at_Sun.COM> wrote:
>>>>
>>>>> The last successful QL run was [1], which happened at 1508 PST
>>>>> on Sept 8. It was 16 hours ago. The check in that went in around
>>>>> that time was rev #* *22477 [2]. There have been 24 check-ins
>>>>> since then. I wonder how those engineers ensured that their
>>>>> changes did not break anything.
>>>>>
>>>>> Thanks,
>>>>> Sahoo
>>>>>
>>>>> [1] http://hudson.sfbay/job/v3-dev-builds-quicklook/1740/
>>>>> [2] http://fisheye4.atlassian.com/changelog/glassfish-svn/trunk/v3?cs=22477
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>