[
https://issues.apache.org/jira/browse/FLINK-30619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680232#comment-17680232
]
Chesnay Schepler commented on FLINK-30619:
------------------------------------------
Can't reproduce it locally. Either a clock issue on the machines causing time
measurements to go backwards or a strange thread visibility issue.
I'm inclined to just add a retry to the test.
> AdaptiveSchedulerTest.testStatusMetrics is not stable
> -----------------------------------------------------
>
> Key: FLINK-30619
> URL: https://issues.apache.org/jira/browse/FLINK-30619
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.16.0, 1.17.0
> Reporter: Matthias Pohl
> Assignee: Chesnay Schepler
> Priority: Critical
> Labels: test-stability
>
> We experience a test instability in
> {{AdaptiveSchedulerTest.testStatusMetrics}}.
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=44635&view=logs&j=0e7be18f-84f2-53f0-a32d-4a5e4a174679&t=7c1d86e3-35bd-5fd5-3b7c-30c126a78702&l=8475
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
