[ 
https://issues.apache.org/jira/browse/FLINK-30539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653606#comment-17653606
 ] 

Matthias Pohl edited comment on FLINK-30539 at 1/3/23 7:07 AM:
---------------------------------------------------------------

-Ok, I assume you meant waiting with investigating the issue which makes sense. 
I went ahead and created the PRs for removing the timeout, though.-

reevaluating my comment: I missed going over [your comment in 
FLINK-24169|https://issues.apache.org/jira/browse/FLINK-24169?focusedCommentId=17653560&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17653560]
 initially. Considering that you want to tackle the relative path issue for 
YARN tests in [PR #21128|https://github.com/apache/flink/pull/21128] that 
covers the hadoop update, it makes sense to wait with investigating this issue. 
Thanks for that. Merging the PRs for removing the timeouts makes sense, anyway.


was (Author: mapohl):
Ok, I assume you meant waiting with investigating the issue which makes sense. 
I went ahead and created the PRs for removing the timeout, though.

> 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, 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)

Reply via email to