[jira] [Resolved] (DERBY-5692) intermittent test failure in storetests/st_derby715.java

["Myrna van Lunteren (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren resolved DERBY-5692.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.9.0.0
                   10.8.2.3
         Assignee: Myrna van Lunteren

Thanks Knut for that theory/explanation.
I followed Mike's suggestion and ran storetests with, and without the additional st_derby715_derby.properties file, and did not see any change in performance on my machine; the entire suite took between 1 and 2 minutes, and the st_derby715 test took 11 or 12 minutes, either way. I ran each with both ibm 142 and 1.6, each with and without the new properties file, and each combination 3 times.
(In passing, I noted that the suite seemed to take about 10 seconds longer with ibm 142 than with 1.6).

I committed the change with revision 1328061 on trunk, and backported to 10.8 with revision 1328075.

I'm resolving this issue; but because without a repro this is a bit of a guess, it can be reopened if the test fails again.

                
> 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.2.3
>         Environment: Windows 2008, 4 CPU, ibm 1.4.2.
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.8.2.3, 10.9.0.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira