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/30 10:42:00 UTC
[jira] [Assigned] (FLINK-30138) BlobServerCleanupTest utilizes failsWithin with a quite low timeout which might result in test instabilities
[ https://issues.apache.org/jira/browse/FLINK-30138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Pohl reassigned FLINK-30138:
-------------------------------------
Assignee: Matthias Pohl
> BlobServerCleanupTest utilizes failsWithin with a quite low timeout which might result in test instabilities
> ------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-30138
> URL: https://issues.apache.org/jira/browse/FLINK-30138
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination, Tests
> Affects Versions: 1.16.0, 1.17.0, 1.15.2
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Major
> Labels: starter
>
> {{BlobServerCleanupTest}} utilizes {{failsWithin}} using a low timeout threshold (100ms) in several locations. This might result in test instabilities (e.g. [here|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43221&view=logs&j=a57e0635-3fad-5b08-57c7-a4142d7d6fa9&t=2ef0effc-1da1-50e5-c2bd-aab434b1c5b7&l=8801]). We shouldn't rely on timeouts as stated in the Flink coding guidelines.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)