[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 ] Andres de la Peña updated CASSANDRA-15338: -- Since Version: 4.0-alpha Source Control Link: https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/50/ Resolution: Fixed Status: Resolved (was: Ready to Commit) > 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 >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Andres de la Peña updated CASSANDRA-15338: -- Status: Ready to Commit (was: Review In Progress) > 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 >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Andres de la Peña updated CASSANDRA-15338: -- Reviewers: Andres de la Peña, Andres de la Peña (was: Andres de la Peña) Andres de la Peña, Andres de la Peña (was: Andres de la Peña) Status: Review In Progress (was: Patch Available) > 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 >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Andres de la Peña updated CASSANDRA-15338: -- Reviewers: Andres de la Peña > 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 >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Yifan Cai updated CASSANDRA-15338: -- Test and Documentation Plan: unit test Status: Patch Available (was: Open) > 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 >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Yifan Cai updated CASSANDRA-15338: -- Bug Category: Parent values: Correctness(12982)Level 1 values: Test Failure(12990) Complexity: Normal Discovered By: Unit Test Severity: Low Assignee: Yifan Cai Status: Open (was: Triage Needed) > 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 >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Yifan Cai updated CASSANDRA-15338: -- Attachment: CASS-15338-Docker.zip > 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 > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] ASF GitHub Bot updated CASSANDRA-15338: --- Labels: pull-request-available (was: ) > 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 > Labels: pull-request-available > Fix For: 4.0-alpha > > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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: -- Fix Version/s: 4.0-alpha > 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 > Fix For: 4.0-alpha > > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org