Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 18 Apr 2012 15:09:42 +0000 (UTC)
From: "Mike Matrigali (Commented) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <468660678.1146.1334761782962.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2109507738.33955.1334686641017.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5692) intermittent test failure in
 storetests/st_derby715.java
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

without a reliable repro hard to say what is going on, which is why I suggested running just that test/suite to see if it pops
easily in that environment.   I am just guessing at why it happens on that platform and not others.  I think the way the locking
code works we don't really know why we have woken up when we sleep waiting for a lock.   If we have not gotten the lock then
we check how long we have waited and if it is under timeout we do the dealock check.

Yes I am suggesting the kind of change you have, but would see how much longer if at all the storetests suite takes with
it.  I don't know how many expected lock timeouts, if any the suite has.
                
> 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