[ 
https://issues.apache.org/jira/browse/CASSANDRA-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708957#comment-17708957
 ] 

Brandon Williams commented on CASSANDRA-18427:
----------------------------------------------

[Here|https://app.circleci.com/pipelines/github/driftx/cassandra/955/workflows/ad33d42f-fa93-4331-b716-68d01138e324/jobs/19120]
 is 500 runs in circle (against trunk, which may be correct?) that 
unsurprisingly did not reproduce.  I believe this was just a timeout, since the 
record with a TTL of 5 is not present, but the one with the longer TTL of 1000 
is.

> Test failure: pdtest: 
> dtest-novnode.ttl_test.TestDistributedTTL.test_ttl_is_respected_on_delayed_replication
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18427
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18427
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/dtest/python
>            Reporter: Josh McKenzie
>            Priority: Normal
>
> {{Failed 1 times in the last 30 runs. Flakiness: 3%, Stability: 96%}}
> {code}
> Error Message
> AssertionError: Expected [[1, 1, None, None], [2, 2, None, None]] from SELECT 
> * FROM ttl_table;, but got [[2, 2, None, None]]
> Stacktrace
> self = <ttl_test.TestDistributedTTL object at 0x7fce080d8c10>
>     def test_ttl_is_respected_on_delayed_replication(self):
>         """ Test that ttl is respected on delayed replication """
>         self.prepare()
>         self.node2.stop()
>         self.session1.execute("""
>             INSERT INTO ttl_table (key, col1) VALUES (1, 1) USING TTL 5;
>         """)
>         self.session1.execute("""
>             INSERT INTO ttl_table (key, col1) VALUES (2, 2) USING TTL 1000;
>         """)
> >       assert_all(
>             self.session1,
>             "SELECT * FROM ttl_table;",
>             [[1, 1, None, None], [2, 2, None, None]]
>         )
> ttl_test.py:480: 
> {code}
> At face value this didn't look like a classic "oops I timed out", but now 
> that I read that error message I'm not as sure. So I'd check that first and 
> just close out if it's a timeout by another name until we get the infra 
> stabilized.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to