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 "Mike Matrigali (JIRA)" <ji...@apache.org> on 2013/06/05 19:10:21 UTC

[jira] [Commented] (DERBY-3624) testfailure in storetests/st_derby715 with ibm 1.5 on iseries machine; one deadlock message missing

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

Mike Matrigali commented on DERBY-3624:
---------------------------------------

test failed in nightly tests against trunk, ibm16, windows:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1485917-derbyall_diff.txt

********* Diff file derbyall/storeall/storetests/st_derby715.diff
*** Start: st_derby715 jdk1.6.0 storeall:storetests 2013-05-23 19:03:56 ***
4 del
< Got a Deadlock.
Test Failed.
*** End:   st_derby715 jdk1.6.0 storeall:storetests 2013-05-23 19:04:09 ***
                
> testfailure in storetests/st_derby715 with ibm 1.5 on iseries machine; one deadlock message missing
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3624
>                 URL: https://issues.apache.org/jira/browse/DERBY-3624
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.4.1.3, 10.8.3.1, 10.11.0.0
>         Environment: iseries, ibm 1.5.: 
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05)
> Classic VM (build 1.5, build JDK-1.5, native threads, jitc_de)
>            Reporter: Myrna van Lunteren
>              Labels: derby_triage10_8
>         Attachments: derby.log, st_derby715.tmp
>
>
> I saw this fail once; a couple of reruns didn't duplicate the problem.
> The only difference appears to be that one of the deadlock messages is missing from the output.
> 4 del
> < Got a Deadlock.

--
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