Amy,
Unfortunately, our build infrastructure has too many regressions. For a
long time now, it has stopped sending email notifications for QL
failures and we all continue to waste our time figuring out which
check-in caused a failure after several hours.
I do not know if your check-in caused the failure, but I found that was
the only check-in around that time. There is a lot of guess-work
involved in our current system to trace such things.
You mentioned you would do a clean build and run tests. What's the
outcome? I am assuming you are checking out upto rev#22477 and doing the
test.
Thanks,
Sahoo
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
>