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-5692) intermittent test failure in storetests/st_derby715.java
Date Fri, 28 Feb 2014 18:42:20 GMT

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

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

Looks like there is still some instability in this test?
It failed here, with jdk 1.8: http://download.java.net/javadesktop/derby/request_5588265/
Date:             2014-02-28 11:55:50 UTC 
Svn branch:  trunk 
Svn revision: 1572665 
diff:
*** Start: st_derby715 jdk1.8.0_05 storeall:storetests 2014-02-28 14:05:15 ***
4 del
< Got a Deadlock.
Test Failed.
*** End:   st_derby715 jdk1.8.0_05 storeall:storetests 2014-02-28 14:06:31 ***


> 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