You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2012/10/24 18:24:14 UTC
[jira] [Assigned] (DERBY-4323) test failure in
lang.ErrorMessageTest with IBM iseries IBM 1.5
[ https://issues.apache.org/jira/browse/DERBY-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen reassigned DERBY-4323:
-----------------------------------------
Assignee: Knut Anders Hatlen
> 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
> Attachments: 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