You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2022/11/04 13:25:00 UTC

[jira] [Resolved] (FLINK-29198) RetryExtension doesn't make the test fail if the retries are exhausted

     [ https://issues.apache.org/jira/browse/FLINK-29198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Pohl resolved FLINK-29198.
-----------------------------------
    Fix Version/s: 1.17.0
                   1.15.3
                   1.16.1
       Resolution: Fixed

master: 733969001036b1263bd798433e229816acff1658
1.16: f4fe35fdf179683f565ae0ee6bc374ed6e85c605
1.15: b68f37cad6dc5207692badfe970ae803143054f4

> RetryExtension doesn't make the test fail if the retries are exhausted
> ----------------------------------------------------------------------
>
>                 Key: FLINK-29198
>                 URL: https://issues.apache.org/jira/browse/FLINK-29198
>             Project: Flink
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 1.15.0, 1.16.0, 1.17.0
>            Reporter: Matthias Pohl
>            Assignee: Ryan Skraba
>            Priority: Major
>              Labels: pull-request-available, starter
>             Fix For: 1.17.0, 1.15.3, 1.16.1
>
>
> 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.



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