Details
Description
FLINK-24627 introduced retry functionality for JUnit5-based tests. It appears that the retry mechanism doesn't have the desired behavior: If the retries are exhausted without the test ever succeeding will result in the test being ignored. I would expect the test to fail in that case. Otherwise, a CI run would succeed without anyone noticing the malfunctioning of the test.
Attachments
Issue Links
- causes
-
FLINK-29891 The RetryRule tests print some excessive stacktraces that might confuse people investigating actual issues
-
- Open
-
- is caused by
-
FLINK-24627 Port JUnit 4 rules to JUnit5 extensions
-
- Closed
-
- Testing discovered
-
FLINK-29245 [JUnit 5 Migration] Remove RetryRule
-
- Open
-
- links to