db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-372) ConcurrentPersistenceManagersSameClasses - Failed on second run
Date Sun, 23 Apr 2006 16:43:06 GMT
    [ http://issues.apache.org/jira/browse/JDO-372?page=comments#action_12375888 ] 

Michael Bouschen commented on JDO-372:

The test uses the same classes with another PersistenceManager (pm2) of the jdo refererence
implementation (JPOX).  It does not make sense to execute the test if the JDO implementation
under test does not support binary compatibility, because then there is gurantee that the
enhanced classes work with the jdo refererence implementation.

One comment about the patch: I propose to delete the pm2 instances in the finally block. Then
they get removed even if the test case fails. What do you think?

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

View raw message