[ https://issues.apache.org/jira/browse/CASSANDRA-17120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440510#comment-17440510 ]
Benjamin Lerer edited comment on CASSANDRA-17120 at 11/8/21, 2:38 PM: ---------------------------------------------------------------------- The issue is that the comparison is done between the output of {{System.currentTimeMillis}} and the output of the {{Clock}} used by the function. The test need to use the output of the {{Clock}} for computing the expected value. was (Author: blerer): The issue is that the comparison is done between the output of {{System.currentTimeMillis}} and the output of the {{Clock}} used but the function. The test need to use the output of the {{Clock}} for computing the expected value. > Flaky test - org.apache.cassandra.serializers.TimestampSerializerTest > --------------------------------------------------------------------- > > Key: CASSANDRA-17120 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17120 > Project: Cassandra > Issue Type: Bug > Components: Test/unit > Reporter: Brandon Williams > Priority: Normal > Fix For: 4.x > > > As seen here: > https://app.circleci.com/pipelines/github/blerer/cassandra/239/workflows/32b4bc10-685a-4719-ac6c-950e76cd9533/jobs/2144 > {noformat} > junit.framework.AssertionFailedError: 'now' timestamp not within expected > tolerance. > at > org.apache.cassandra.serializers.TimestampSerializerTest.testNow(TimestampSerializerTest.java:227) > {noformat} -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org