Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9F7BDD5C6 for ; Thu, 25 Oct 2012 17:01:13 +0000 (UTC) Received: (qmail 99649 invoked by uid 500); 25 Oct 2012 17:01:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 99601 invoked by uid 500); 25 Oct 2012 17:01:13 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 99347 invoked by uid 99); 25 Oct 2012 17:01:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2012 17:01:13 +0000 Date: Thu, 25 Oct 2012 17:01:12 +0000 (UTC) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Message-ID: <93353477.28157.1351184473022.JavaMail.jiratomcat@arcas> Subject: [jira] [Comment Edited] (DERBY-4323) test failure in lang.ErrorMessageTest with IBM iseries IBM 1.5 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484204#comment-13484204 ] Myrna van Lunteren edited comment on DERBY-4323 at 10/25/12 4:59 PM: --------------------------------------------------------------------- Thank you for looking into this failure! I did not see this failure in the testing for any more recent releases on this OS (i.e. ibm iseries - not for any 10.8 release (or candidate), nor 10.9). I think this coincides with a change in hardware and OS version. I can't remember having seen this anywhere else (I usually add a comment in an open test issue if I see it again, and I have not done that for this one, so it's likely I didn't see it again). I think closing is appropriate, and if this occurs again, we can reopen or open a new issue. I'm resolving instead of closing, in case we want to backport this. was (Author: myrna): Thank you for looking into this failure! I did not see this failure in the testing for any more recent releases on this OS (i.e. ibm iseries - not for any 10.8 release (or candidate), nor 10.9). I think this coincides with a change in hardware. I can't remember having seen this anywhere else (I usually add a comment in an open test issue if I see it again, and I have not done that for this one, so it's likely I didn't see it again). I think closing is appropriate, and if this occurs again, we can reopen or open a new issue. I'm resolving, in case we want to backport this. > test failure in lang.ErrorMessageTest with IBM iseries IBM 1.5 > -------------------------------------------------------------- > > Key: DERBY-4323 > URL: https://issues.apache.org/jira/browse/DERBY-4323 > Project: Derby > Issue Type: Bug > Components: Test > Affects Versions: 10.5.2.0 > Environment: IBM iseries, OS: AS/400; OS version: V5R4M0, IBM 1.5 (1.5.0_13-b05) > Reporter: Myrna van Lunteren > Assignee: Knut Anders Hatlen > Priority: Minor > Labels: derby_triage10_8 > Fix For: 10.10.0.0 > > Attachments: d4323-1a.diff, ErrorMessageTest_derby.log, error-stacktrace.out > > > There was this error during the 10.5.2.0 test run - when the ErrorMessageTest was run by itself later there was no problem, and neither did this show up during the ibm 1.6 run: > 1) testDeadlockTimeout(org.apache.derbyTesting.functionTests.tests.lang.ErrorMessageTest)junit.framework.ComparisonFailure: Not a deadlock expected:<...001> but was:<...XL2> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira