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] Updated: (JDO-372) ConcurrentPersistenceManagersSameClasses - Failed on second run
Date Sun, 23 Apr 2006 18:06:06 GMT
     [ http://issues.apache.org/jira/browse/JDO-372?page=all ]

Michael Bouschen updated JDO-372:

    Component: tck20
      Version: JDO 2 rc1
    Assign To: Michael Bouschen

Thanks for the review. 

You find the exclude list in tck20/src/conf/exclude.list. It is automatically taken into account
when running the tck from maven (e.g maven runtck.jdori or maven runtck.iut).

> ConcurrentPersistenceManagersSameClasses - Failed on second run
> ---------------------------------------------------------------
>          Key: JDO-372
>          URL: http://issues.apache.org/jira/browse/JDO-372
>      Project: JDO
>         Type: Bug

>   Components: tck20
>     Versions: JDO 2 rc1
>     Reporter: Ilan Kirsh
>     Assignee: Michael Bouschen
>  Attachments: JDO-372-mbo.patch, 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