[ http://issues.apache.org/jira/browse/DERBY-1640?page=comments#action_12425795 ] Deepa Remesh commented on DERBY-1640: -------------------------------------
If we look at the tinderbox results, this test started failing here: http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/Limited/testSummary-428125.html Two changes went in for this run out of which the candidate causing this is likely DERBY-1579 which falls into the category (change to system catalogs) explained by Mike. I had also seen this diff with the patch for DERBY-1579 and noted the peculiar diff here: http://issues.apache.org/jira/browse/DERBY-1579#action_12425246 I had not understood how the particular change could cause this diff. Thanks Mike for explaining the possible causes. > Instability in XATest > --------------------- > > Key: DERBY-1640 > URL: http://issues.apache.org/jira/browse/DERBY-1640 > Project: Derby > Issue Type: Bug > Components: Test, Regression Test Failure > Affects Versions: 10.2.0.0 > Reporter: Rick Hillegas > Fix For: 10.2.0.0 > > > I am seeing the following diff in XATest, in a clean subversion client > running under DerbyNetClient framework on jdk14 on either Linux or cygwin/xp: > 52a53 > > (1 |PREPARED |false |APP |UserTransaction > 54d54 > < (1 |PREPARED |false |APP |UserTransaction > Test Failed. > *** End: XATest jdk1.4.2_08 DerbyNetClient 2006-08-03 13:06:22 *** > Looks like an ordering instability. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
