[
https://issues.apache.org/jira/browse/FLINK-16572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101635#comment-17101635
]
Robert Metzger commented on FLINK-16572:
----------------------------------------
Thanks a lot!
Yes, debugging these rarely occurring issues is quite annoying.
You can open a draft PR and push dummy commits to trigger CI. Note that we use
"flinkbot", which takes up to 30 minutes for picking up a commit, and does some
magic with branches to "flink-ci/flink".
This issue is occurring quite rarely (once a week, which is probably 1/350
builds fail with this). Maybe it would make more sense to carefully add some
debug statements specifically to this test (only in the test code, we don't
want to release testing code in the upcoming Flink 1.11 :) ). If that helps,
I'm willing to consider & merge :)
> CheckPubSubEmulatorTest is flaky on Azure
> -----------------------------------------
>
> Key: FLINK-16572
> URL: https://issues.apache.org/jira/browse/FLINK-16572
> Project: Flink
> Issue Type: Bug
> Components: Build System / Azure Pipelines, Connectors / Google
> Cloud PubSub
> Affects Versions: 1.11.0
> Reporter: Aljoscha Krettek
> Assignee: Richard Deurwaarder
> Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Log:
> https://dev.azure.com/aljoschakrettek/Flink/_build/results?buildId=56&view=logs&j=1f3ed471-1849-5d3c-a34c-19792af4ad16&t=ce095137-3e3b-5f73-4b79-c42d3d5f8283&l=7842
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
