[
https://issues.apache.org/jira/browse/FLINK-23611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405735#comment-17405735
]
Matthias commented on FLINK-23611:
----------------------------------
As a summary, I wasn't able to verify System input/output stream reset locally.
But it shouldn't have an effect on the test since the Runner instances still
hold a reference to the actual `PrintStream` instances being used for the
"stop" command.
We are not able to investigate anything on the Flink side due to the missing
Flink logs. Our guess is that the join made the test halt forever. AzureCI
killed the JVM at the end. The after-test log collection couldn't be executed.
I added timeouts for the job submission and the YARN Session Cluster shutdown
trigger. Additionally, I added some additional logs and fixed a minor bug.
> YARNSessionCapacitySchedulerITCase.testVCoresAreSetCorrectlyAndJobManagerHostnameAreShownInWebInterfaceAndDynamicPropertiesAndYarnApplicationNameAndTaskManagerSlots
> hangs on azure
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-23611
> URL: https://issues.apache.org/jira/browse/FLINK-23611
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.14.0, 1.12.5
> Reporter: Xintong Song
> Assignee: Matthias
> Priority: Major
> Labels: pull-request-available, test-stability
> Fix For: 1.14.0, 1.12.6
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=21439&view=logs&j=245e1f2e-ba5b-5570-d689-25ae21e5302f&t=e7f339b2-a7c3-57d9-00af-3712d4b15354&l=28959
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
