[
https://issues.apache.org/jira/browse/FLINK-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163183#comment-17163183
]
Yun Tang commented on FLINK-18335:
----------------------------------
[~rmetzger] I cannot produce this locally and I also try to trigger CI of tests
more than 40+ times (
https://dev.azure.com/myasuka/flink/_build/results?buildId=183&view=results and
more), however, still cannot reproduce it.
Since notify checkpoint abort message is sent asynchronously, there existed the
possibility for time out. I think we could create another PR to increase the
time out and add necessary logs so that we could know what's wrong if meet this
error next time, what do you think?
> NotifyCheckpointAbortedITCase.testNotifyCheckpointAborted time outs
> --------------------------------------------------------------------
>
> Key: FLINK-18335
> URL: https://issues.apache.org/jira/browse/FLINK-18335
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing, Tests
> Affects Versions: 1.12.0
> Reporter: Piotr Nowojski
> Assignee: Yun Tang
> Priority: Critical
> Labels: test-stability
> Fix For: 1.12.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=3582&view=logs&j=5c8e7682-d68f-54d1-16a2-a09310218a49&t=f508e270-48d6-5f1e-3138-42a17e0714f0
> {noformat}
> [ERROR] Errors:
> [ERROR]
> NotifyCheckpointAbortedITCase.testNotifyCheckpointAborted:182->verifyAllOperatorsNotifyAborted:195->Object.wait:502->Object.wait:-2
> ยป TestTimedOut
> {noformat}
> CC [~yunta]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
