db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-4323) test failure in lang.ErrorMessageTest with IBM iseries IBM 1.5
Date Thu, 25 Oct 2012 15:49:12 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Myrna van Lunteren resolved DERBY-4323.

       Resolution: Fixed
    Fix Version/s:

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:
>         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:
>         Attachments: d4323-1a.diff, ErrorMessageTest_derby.log, error-stacktrace.out
> There was this error during the 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

View raw message