[
https://issues.apache.org/jira/browse/CASSANDRA-16728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16728:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990)
Complexity: Low Hanging Fruit
Discovered By: Unit Test
Fix Version/s: NA
Severity: Low
Status: Open (was: Triage Needed)
> Fix flaky test
> pushed_notifications_test.py::TestVariousNotifications::test_tombstone_failure_threshold_message
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16728
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: NA
>
>
> The test
> pushed_notifications_test.py::TestVariousNotifications::test_tombstone_failure_threshold_message
> checks for the log message "Scanned over.* tombstones.* query aborted”, but
> this can happen on any node, so it will timeout checking node1 then check the
> other nodes; when this happens it checks that the returned result equals
> "Cannot find tombstone failure threshold error in log after failed query”,
> which isn’t possible as the return is matching log lines, this should be
> replaced by checking for failure truthiness.
--
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
