[
https://issues.apache.org/jira/browse/CASSANDRA-17033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441252#comment-17441252
]
David Capwell commented on CASSANDRA-17033:
-------------------------------------------
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17033-trunk-55120AA3-A9C0-46B7-A831-0B7249750D7E]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17033-trunk-55120AA3-A9C0-46B7-A831-0B7249750D7E]|[build|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1270/]|
> MessagingServiceTest listenOptionalSecureConnection and
> listenRequiredSecureConnection fail sporadically
> --------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17033
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17033
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
> Reporter: Caleb Rackliffe
> Assignee: David Capwell
> Priority: Normal
> Labels: test-failure, test-failures
> Fix For: 4.x
>
>
> This popped up in a recent CircleCI run:
> https://app.circleci.com/pipelines/github/maedhroz/cassandra/351/workflows/f8dbf599-df72-4982-8a12-a72a5b8ddd3b/jobs/2195
> I was able to reproduce it locally on trunk as well in a single run, although
> it happens perhaps once per 3-4 runs of the MessagingServiceTest suite. It
> looks like we open the sockets in an InboundSockets container, await on the
> future that returns, and then assert that all those sockets are open. It’s
> not clear to me yet why this assertion fails sporadically, or what state
> changes exactly are racing.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
