| Michael Bouschen (JIRA) 2006-04-24, 7:58 am |
| [ http://issues.apache.org/jira/browse/JDO-372?page=all ]
Michael Bouschen updated JDO-372:
---------------------------------
Attachment: JDO-372-mbo.patch
I extended Craig's patch and added two things:
- Exit the test method if the binary compatibility option is not supported.
- Remove pm2 instances in the finally block of the test method.
Please have a look.
Ilan,
you are right, the enhancement tests need to check the binary compatibiliyt option, too. But since they are on the TCK exclude list, they are currently not executed.
> 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-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 fai
l 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/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|