[
https://issues.apache.org/jira/browse/DERBY-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484007#comment-13484007
]
Knut Anders Hatlen commented on DERBY-4323:
-------------------------------------------
Committed revision 1402043.
It's difficult to say if this is enough to fix the problem, since it's so hard
to reproduce. Should we resolve for now and reopen/file a new report if it
happens again?
> 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: 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
