[
https://issues.apache.org/jira/browse/FLINK-30539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30539:
-----------------------------------
Labels: pull-request-available stale-major test-stability (was:
pull-request-available test-stability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> YARNSessionCapacitySchedulerITCase.testDetachedPerJobYarnCluster and
> testDetachedPerJobYarnClusterWithStreamingJob timing out
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-30539
> URL: https://issues.apache.org/jira/browse/FLINK-30539
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.16.0
> Reporter: Matthias Pohl
> Priority: Major
> Labels: pull-request-available, stale-major, test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=44337&view=logs&j=298e20ef-7951-5965-0e79-ea664ddc435e&t=d4c90338-c843-57b0-3232-10ae74f00347&l=32023
> In order to help investigating the issue: Both tests failed because they are
> running into the 60s timeout that was defined for each of them. We should get
> rid of the timeout to access the thread dump. It might be related to
> FLINK-24169
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
