db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dyre.Tjeldv...@Sun.COM
Subject Re: Showstoppers
Date Thu, 27 Mar 2008 18:24:38 GMT
Mike Matrigali <mikem_app@sbcglobal.net> writes:

> Dyre.Tjeldvoll@Sun.COM wrote:
>> Is there an existing bug in Derby which you consider to be a showstopper for
>> 10.4? (Meaning that you will veto the release unless this bug gets fixed).
>> If this bug is not being actively worked on, please flag it here ASAP,
>> so that those looking for bugs to fix can consider it.
>> I hope that many people will find the time to fix bugs for 10.4 :)
>> Thanks,
> I think it would be good to minimally get down to a clean regression
> suite run before releasing, or at least investigate and say why not
> necessary to fix for the release.  

Agreed. +1

> Having continuing "expected" failures just makes it even harder to
> support the release.


> Here are some of the latest public test result runs with failures:
> http://dbtg.thresher.com/derby/test/10.4Branch/jvm1.5/testing/Limited/testSummary-640905.html
> http://dbtg.thresher.com/derby/test/10.4Branch/jvm1.5/testing/Limited/testSummary-640905.html
> http://dbtg.thresher.com/derby/test/10.4Branch/jvm1.6/testing/Limited/testSummary-640905.html
> on quick inspection I think that means fixing:
> DERBY-3561 -
> TestStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError:
> expected:<2> but was:<5>

I was hoping that someone was looking at this...

> There are a number of network connection errors, maybe someone can
> comment on whether these are test issues or environment.  There is not
> history
> available for the test runs so I don't know if these are new or not.

Seems like they only occured with jvm 1.5? I agree that it would be good
get some clarification here...


View raw message