[
https://issues.apache.org/jira/browse/FLINK-32478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738944#comment-17738944
]
Rui Fan commented on FLINK-32478:
---------------------------------
{quote} I don't think we can treat them as same ci runs at least because it's
not cherry pick (changes are not identical)
{quote}
Actually, the first commit of them are cherry pick. I developed the master
commit, and cherry pick to 1.16 and 1.17.
Also, I added a limitation for master PR based on this bug.
Why do I prefer to run only 1 time?
* It blocks all CIs, I want to fix it asap. Each separate CI run takes 4 hours
and I'm afraid we won't be able to fix it today.
* They are cherry pick, 3 different PRs can show whether the problem has been
fixed.
* I run the failed test on my Mac more than 1K times.
Of course, running CI of each PR three times is more robust. If all of you
think it's necessary, I will follow it.
> SourceCoordinatorAlignmentTest.testAnnounceCombinedWatermarkWithoutStart fails
> ------------------------------------------------------------------------------
>
> Key: FLINK-32478
> URL: https://issues.apache.org/jira/browse/FLINK-32478
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Common
> Affects Versions: 1.18.0, 1.16.3, 1.17.2
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Blocker
> Labels: pull-request-available, test-stability
> Fix For: 1.18.0, 1.16.3, 1.17.2
>
>
> SourceCoordinatorAlignmentTest.testAnnounceCombinedWatermarkWithoutStart fails
>
> Root cause: multiple sources share the same thread pool, and the second
> source cannot start due to the first source closes the shared thread pool.
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=50611&view=logs&j=0da23115-68bb-5dcd-192c-bd4c8adebde1&t=24c3384f-1bcb-57b3-224f-51bf973bbee8&l=8613
--
This message was sent by Atlassian Jira
(v8.20.10#820010)