[CASSANDRA-19198] [Analytics] Flaky test: SSTableInputStreamTests#testTimeoutShouldAccountForActivityTime

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: NA
• Component/s: Analytics Library
• Bug Category: Code - Bug - Unclear Impact
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: Unit Test
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra-analytics/commit/bbfca46129992e83055ba9b0b4f836871eef0990

Test and Documentation Plan

CI

• Assignee: Yifan Cai
• Reporter: Yifan Cai

Authors

Yifan Cai

Reviewers

Francisco Guerrero

• Created: 12/Dec/23 16:28
• Updated: 13/Dec/23 15:37
• Resolved: 13/Dec/23 15:37

Description

The test case uses relative time value for assertion. It is flaky since test execution could be delayed depending on the test environment.

Error Message

org.opentest4j.AssertionFailedError: Timeout didn't account for activity time. Took 1219ms should have taken at most 1100ms ==> expected: <true> but was: <false> 

Stacktrace

org.opentest4j.AssertionFailedError: Timeout didn't account for activity time. Took 1219ms should have taken at most 1100ms ==> expected: <true> but was: <false>
at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
at app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:211)
at app//org.apache.cassandra.spark.utils.SSTableInputStreamTests.testTimeoutShouldAccountForActivityTime(SSTableInputStreamTests.java:234)
... 

Issue Links

• links to: GitHub Pull Request #26