Donald, Rick's recent commit cleaned up the majority of the failures, but the two you pointed out remain. They appear to be related to using the same named entity in multiple tests. I traced the failure back to rev 826264, which should not have caused these failures. However, that commit did disable a test which may have changed the run order of tests. That, combined with using duplicate table names is the likely suspect. I'm working on a fix.
-Jeremy On Wed, Oct 21, 2009 at 1:36 PM, Rick Curtis <[email protected]> wrote: > A number of the failures from from today are due to r828072 (as pointed out > in a earlier email by Jeremy). I'm running a Team City build right with a > few updates and should have those changes change in later on this > afternoon(if all goes well). > > -Rick > > On Wed, Oct 21, 2009 at 1:17 PM, Donald Woods <[email protected]> wrote: > > > Last nights automated builds had 2 new test failures on Derby with IBM 5 > > SDK, IBM 6 SDK and Sun 6 JDK (but not Sun 5 JDK) that seem related to one > of > > the following 2 commits - > > r827727 - Jeremy > > r827788 - Pinaki > > > > Since then, we are now seeing even more test failures due to some commits > > today. The latest failure counts are - > > Derby IBM 6 SDK - 37 failures > > Derby IBM 5 SDK - 26 failures > > Derby Sun 5 JDK - 26 failures > > Derby Sun 6 SDK - 18 failures > > > > > > -Donald > > >
