You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/04 13:51:00 UTC

[jira] [Commented] (BEAM-8210) Python Integration tests: log test name

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

Danny McCormick commented on BEAM-8210:
---------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/19867

> Python Integration tests: log test name
> ---------------------------------------
>
>                 Key: BEAM-8210
>                 URL: https://issues.apache.org/jira/browse/BEAM-8210
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow, sdk-py-core, testing
>            Reporter: Udi Meiri
>            Priority: P3
>              Labels: beam-fixit
>
> When creating a job (on any runner), log the originating test so it's easier to debug.
> Postcommits frequently run tens of pipelines at a time and it's getting harder to tell them apart.
> By logging I mean putting it somewhere in the job proto (such as in parameter, job name, etc.). Using the worker logger on startup won't work if the worker fails to start.
> Ideally you should be able to see the name in the runner UI (such as Dataflow cloud console).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)