[
https://issues.apache.org/jira/browse/DERBY-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876894#comment-13876894
]
Myrna van Lunteren commented on DERBY-5692:
-------------------------------------------
failed 1/17/2014 on windows 2208, with 10.8.3.3 (1559308) with ibm1.6:
http://people.apache.org/~myrnavl/derby_test_results/v10_8/windows/testlog/ibm16/1559308-derbyall_diff.txt
diff:
4 del
< Got a Deadlock.
> 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)
