[
https://issues.apache.org/jira/browse/DERBY-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233935#comment-13233935
]
Knut Anders Hatlen commented on DERBY-5643:
-------------------------------------------
I mentioned in an earlier comment that the compatibility tests in Oracle's
nightly test runs had problems after the fix went in. That wasn't quite true.
When looking closer at the test reports, it turned out it was suites.All that
had problems. It looks like it got stuck in the replication tests on all
platforms except Windows. And the tinderbox has hung in a similar state since
Thursday (it did however run successfully twice after the fix for this issue
was checked in, but I have no doubt it was the changes in this issue that
caused the problems). I haven't been able to reproduce these hangs in my own
environment yet.
The nightly tests haven't run with the latest fix for this issue yet, because
the Svn EU mirror was down when the tests were supposed to start last night.
Looks like they're running now, and so far two Solaris platforms have completed
their suites.All runs -
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-1302996.html.
Not sure if that means the problem is fixed, as it appears to be intermittent.
I guess we know more in a couple of hours when the results from the other
platforms appear.
> Occasional hangs in replication tests on Linux
> ----------------------------------------------
>
> Key: DERBY-5643
> URL: https://issues.apache.org/jira/browse/DERBY-5643
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.9.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.9.0.0
>
> Attachments: fail-on-timeout.diff, higher-timeout.diff,
> thread-dump.txt, waitFor-2.diff, waitFor.diff
>
>
> We occasionally see hangs in the replication tests on Linux. For example
> here:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/sles/1298470-suitesAll_diff.txt
> This test run was stuck in tearDown() after
> ReplicationRun_Local_Derby4910.testSlaveWaitsForMaster(). (Waiting for
> Thread.join() to return.)
--
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
