db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5692) intermittent test failure in storetests/st_derby715.java
Date Tue, 17 Apr 2012 19:03:17 GMT

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

Mike Matrigali commented on DERBY-5692:
---------------------------------------

Is it likely the machine is heavily loaded with other stuff running while the derbyall for
1.4.2 is running?  I think that timeout
could be returned in this case.  I would suggest changing the defaults for that test to make
deadlock checking something like
1 second and timeout testing something like 1 minute, to make sure machine load does not adversely
affect results.  

Can you run that test 100 times alone on the machine and see any failures?
                
> 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
>            Priority: Minor
>
> 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

        

Mime
View raw message