[
https://issues.apache.org/jira/browse/FLINK-30138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641105#comment-17641105
]
Matthias Pohl commented on FLINK-30138:
---------------------------------------
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43606&view=logs&j=0e7be18f-84f2-53f0-a32d-4a5e4a174679&t=7c1d86e3-35bd-5fd5-3b7c-30c126a78702&l=8389
> 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
> 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)
