You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2019/09/27 17:43:00 UTC
[jira] [Updated] (CASSANDRA-15338) Fix flakey testMessagePurging -
org.apache.cassandra.net.ConnectionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Capwell updated CASSANDRA-15338:
--------------------------------------
Description:
Example failure: [https://circleci.com/gh/dcapwell/cassandra/11#artifacts/containers/1]
{code:java}
Testcase: testMessagePurging(org.apache.cassandra.net.ConnectionTest): FAILED
expected:<0> but was:<1>
junit.framework.AssertionFailedError: expected:<0> but was:<1>
at org.apache.cassandra.net.ConnectionTest.lambda$testMessagePurging$38(ConnectionTest.java:625)
at org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:258)
at org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:231)
at org.apache.cassandra.net.ConnectionTest.testMessagePurging(ConnectionTest.java:584){code}
Looking closer at org.apache.cassandra.net.OutboundConnection.Delivery#stopAndRun it seems that the run method is called before org.apache.cassandra.net.OutboundConnection.Delivery#doRun which may lead to a test race condition where the CountDownLatch completes before executing
was:
Example failure: [https://circleci.com/gh/dcapwell/cassandra/11#artifacts/containers/1]
Testcase: testMessagePurging(org.apache.cassandra.net.ConnectionTest): FAILED
expected:<0> but was:<1>
junit.framework.AssertionFailedError: expected:<0> but was:<1>
at org.apache.cassandra.net.ConnectionTest.lambda$testMessagePurging$38(ConnectionTest.java:625)
at org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:258)
at org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:231)
at org.apache.cassandra.net.ConnectionTest.testMessagePurging(ConnectionTest.java:584)
Looking closer at org.apache.cassandra.net.OutboundConnection.Delivery#stopAndRun it seems that the run method is called before org.apache.cassandra.net.OutboundConnection.Delivery#doRun which may lead to a test race condition where the CountDownLatch completes before executing
> Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-15338
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15338
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: David Capwell
> Priority: Normal
>
> Example failure: [https://circleci.com/gh/dcapwell/cassandra/11#artifacts/containers/1]
>
> {code:java}
> Testcase: testMessagePurging(org.apache.cassandra.net.ConnectionTest): FAILED
> expected:<0> but was:<1>
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
> at org.apache.cassandra.net.ConnectionTest.lambda$testMessagePurging$38(ConnectionTest.java:625)
> at org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:258)
> at org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:231)
> at org.apache.cassandra.net.ConnectionTest.testMessagePurging(ConnectionTest.java:584){code}
>
> Looking closer at org.apache.cassandra.net.OutboundConnection.Delivery#stopAndRun it seems that the run method is called before org.apache.cassandra.net.OutboundConnection.Delivery#doRun which may lead to a test race condition where the CountDownLatch completes before executing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org