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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2013/09/13 20:13:52 UTC
[jira] [Commented] (DERBY-5692) intermittent test failure in
storetests/st_derby715.java
[ https://issues.apache.org/jira/browse/DERBY-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766743#comment-13766743 ]
Mamta A. Satoor commented on DERBY-5692:
----------------------------------------
The test failed again. This time on 10.10.1.3 - (1522131)IBM jdk 1.6 on Windows machine. http://people.apache.org/~myrnavl/derby_test_results/v10_10/windows/testlog/ibm16/1522131-derbyall_diff.txt
*** Start: st_derby715 jdk1.6.0 storeall:storetests 2013-09-11 20:55:59 ***
4 del
< Got a Deadlock.
Test Failed.
*** End: st_derby715 jdk1.6.0 storeall:storetests 2013-09-11 20:56:14 ***
> 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 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