Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 5480 invoked from network); 23 Apr 2006 14:57:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Apr 2006 14:57:15 -0000 Received: (qmail 69625 invoked by uid 500); 23 Apr 2006 14:57:14 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 69614 invoked by uid 99); 23 Apr 2006 14:57:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Apr 2006 07:57:14 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Apr 2006 07:57:13 -0700 Received: from brutus (localhost.localdomain [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 651277142B5 for ; Sun, 23 Apr 2006 14:56:06 +0000 (GMT) Message-ID: <12229072.1145804166405.JavaMail.jira@brutus> Date: Sun, 23 Apr 2006 14:56:06 +0000 (GMT+00:00) From: "Craig Russell (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Updated: (JDO-372) ConcurrentPersistenceManagersSameClasses - Failed on second run In-Reply-To: <26999416.1145727365880.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JDO-372?page=all ] Craig Russell updated JDO-372: ------------------------------ Attachment: JDO-372.patch Please review this patch. I noticed that this test will fail if the implementation does not support binary compatibility, since the classes will not be compatible with the reference implementation if enhanced without regard for 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