db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilan Kirsh (JIRA)" <j...@apache.org>
Subject [jira] Created: (JDO-372) ConcurrentPersistenceManagersSameClasses - Failed on second run
Date Sat, 22 Apr 2006 17:36:05 GMT
ConcurrentPersistenceManagersSameClasses - Failed on second run

         Key: JDO-372
         URL: http://issues.apache.org/jira/browse/JDO-372
     Project: JDO
        Type: Bug

    Reporter: Ilan Kirsh

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:
For more information on JIRA, see:

View raw message