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] Commented: (DERBY-4323) test failure in lang.ErrorMessageTest with IBM iseries IBM 1.5
Date Thu, 02 Dec 2010 21:50:11 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966295#action_12966295
] 

Myrna van Lunteren commented on DERBY-4323:
-------------------------------------------

I saw this again while testing 10.7.1.0 and again with 10.7.1.1 - but both times only with
ibm 1.6, not ibm 1.5. Note that it didn't fail during the 10.6.2.0 nor 10.6.2.1 test runs,
using the same os & jvm versions.
In short, it seems somewhat intermittent.

I am hesitant to increase the deadlocktimeout in the test, wouldn't that make the test slow
down always? 
On the other hand, it's bothersome to have another intermittent failure if there's no bug,
and I also don't want to add yet another optional flag. I'll experiment modifying the test
to force the failure, then decide...


> 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
>            Priority: Minor
>         Attachments: error-stacktrace.out, ErrorMessageTest_derby.log
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message