[
https://issues.apache.org/jira/browse/CASSANDRA-15996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214434#comment-17214434
]
Berenguer Blasi commented on CASSANDRA-15996:
---------------------------------------------
The only 2 things that came to my mind are:
- On node start, instead of relying on the patient cql connection, lets add
flags to wait for the binary protocol and other startup stuff to complete i.e .
But this is just a stab in the dark based on previous experience fixing tests.
Just in case there is some esoteric race at startup.
- {{NoSpamLogger}} has some shuffling of instances around that _maybe_ have a
concurrency hole, _maybe_ I am just imagining things. I have to look at it for
a while a bit longer to make up my mind. In any case I didn't see how that
could affect in this particular case were usage is pretty straightforward and
not multithreaded. So I am also at a loss here so far as well.
> Fix flaky python dtest test_expiration_overflow_policy_capnowarn -
> ttl_test.TestTTL
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-15996
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15996
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: David Capwell
> Assignee: Adam Holmberg
> Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/361/workflows/3a42fa45-1f60-4c95-86a4-15a6773e384e/jobs/1860
> {code}
> > assert warning, 'Log message should be print for CAP and
> > CAP_NOWARN policy'
> E AssertionError: Log message should be print for CAP and
> CAP_NOWARN policy
> E assert []
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
