db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5692) intermittent test failure in storetests/st_derby715.java
Date Wed, 29 Jan 2014 18:46:11 GMT

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

ASF subversion and git services commented on DERBY-5692:
--------------------------------------------------------

Commit 1562544 from [~myrna] in branch 'code/branches/10.8'
[ https://svn.apache.org/r1562544 ]

DERBY-3624; testfailure in storetests/st_derby715 with ibm 1.5 on iseries machine; one deadlock
message missing
DERBY-5692; intermittent test failure in storetests/st_derby715.java
   merge of revision 1530796 from 10.10 branch

> intermittent test failure in storetests/st_derby715.java
> --------------------------------------------------------
>
>                 Key: DERBY-5692
>                 URL: https://issues.apache.org/jira/browse/DERBY-5692
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.8.3.0
>         Environment: Windows 2008, 4 CPU, ibm 1.4.2.
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.8.3.0, 10.9.1.0
>
>
> I am seeing an irregularly occurring failure with ibm 1.4.2 on one machine - which happens
to be the only 4 CPU machine and the only one running Windows 2008...And I've got 10.8 nightly
tests running on it.
> I have not seen this with other jvms on the same machine.
> It's possible this would also happen on trunk, but we stopped supporting 1.4.2 with trunk
and so I do not run tests against trunk with (ibm) 1.4.2.
> When the test passes, the output contains 5 identical lines 'Got a Deadlock'.
> The test failures are of 2 kinds:
> - 1 (or more?) of the 'Got a Deadlock' lines is missing
> - we get a '40XL1' error (timeout) instead of a deadlock.
> As the second situation seems to match what DERBY-715 was about, I thought it worthwhile
reporting as a separate JIRA. We should check it's not somehow a regression.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message