[jira] [Updated] (FLINK-25514) YARN session tests scan unrelated logs for bugs

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-25514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-25514:
-----------------------------------
    Labels: stale-minor test-stability  (was: 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 Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> YARN session tests scan unrelated logs for bugs
> -----------------------------------------------
>
>                 Key: FLINK-25514
>                 URL: https://issues.apache.org/jira/browse/FLINK-25514
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>    Affects Versions: 1.15.0, 1.13.5, 1.14.2
>            Reporter: Niklas Semmler
>            Priority: Minor
>              Labels: stale-minor, test-stability
>
> Many YARN tests that inherit from _org.apache.flink.yarn.YarnTestBase_ deploy a Flink cluster via YARN. The class provides the method _ensureNoProhibitedStringInLogFiles_ to scans the Flink cluster log files for exceptions. 
> At its current state the method cannot distinguish between log files from different test cases that are part of the same test class. (E.g., _org.apache.flink.yarn.YARNSessionFIFOSecuredITCase#testDetachedModeSecureWithPreInstallKeytab_ and {_}org.apache.flink.yarn.YARNSessionFIFOSecuredITCase#testDetachedMode{_}) Thereby, test cases fail only due to a failure of an earlier test case. (E.g., _testDetachedMode_ fails due to a failure of {_}testDetachedModeSecureWithPre{_}{_}InstallKeytab{_})
> The filtering method should be improved, to make failures better understandable. To this end, the filtering method needs to filter on the container suffix of the path. For the YARN container name _container_1640947393046_0001_01_000001_ it needs to map the _0001_ part to the number of the test case considering only test cases that spawn clusters. Or/and the naming of the containers need to be adapted to make this easier. An alternative solution would be to start one YARN cluster per test case (instead of as per test class).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)