You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias (Jira)" <ji...@apache.org> on 2021/05/10 09:42:00 UTC

[jira] [Comment Edited] (FLINK-22614) Provide build artifacts for YARN e2e tests

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

Matthias edited comment on FLINK-22614 at 5/10/21, 9:41 AM:
------------------------------------------------------------

{quote}
Matthias let's include the yarn logs also in the build artifacts.
{quote}

I updated the Jira issue's description to be more specific.


was (Author: mapohl):
{quote}
Matthias let's include the yarn logs also in the build artifacts.
{quote}

I updated the Jira issue's description.

> Provide build artifacts for YARN e2e tests
> ------------------------------------------
>
>                 Key: FLINK-22614
>                 URL: https://issues.apache.org/jira/browse/FLINK-22614
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System / Azure Pipelines
>    Affects Versions: 1.14.0
>            Reporter: Matthias
>            Priority: Major
>              Labels: starter
>
> The YARN e2e don't publish the artifacts if the build failed. Instead, we have to rely on the printout of the watchdog process that prints all the artifacts' content to stdout. This is tedious when analyzing specific artififacts as we have to jump to specific lines in a single log file instead of selecting the relevant artifact from the build artifact archive.
> FYI: Anything that's collected in {{debug_copy_and_show_logs}} of {{flink-end-to-end-tests/test-scripts/common_yarn_docker.sh}} should be included in the build artifacts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)