[ http://issues.apache.org/jira/browse/JDO-372?page=comments#action_12375885 ]
Ilan Kirsh commented on JDO-372: -------------------------------- I don't understand the last comment. I am working now on ObjectDB 2.0 that unlike ObjectDB 1.0 will not support binary compatibility, but the test case passes now. Anyway, I remember that in some cases (maybe in this specific test), I had to use a clean database also to pass the JDOTCK 1.0 with ObjectDB 1.0 that did support binary compatibility. > ConcurrentPersistenceManagersSameClasses - Failed on second run > --------------------------------------------------------------- > > Key: JDO-372 > URL: http://issues.apache.org/jira/browse/JDO-372 > Project: JDO > Type: Bug > Reporter: Ilan Kirsh > Attachments: JDO-372.patch, JDO-372.patch > > Thanks to deleteTearDownClasses / deleteTearDownInstances, most test cases > can run on either a clean database or on an existing database. Unfortunately, > it seems that org.apache.jdo.tck.ConcurrentPersistenceManagersSameClasses is > different. Old objects are not deleted from the 2nd database that this test > case uses, so findPoint may return more than one result object, and the first > result that is checked might be an old object from a previous run. Therefore, > the test case passes the first run and may fail on any additional run on the > same database files. -- 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
