[
https://issues.apache.org/jira/browse/BEAM-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122646#comment-17122646
]
Beam JIRA Bot commented on BEAM-8210:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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.3.4#803005)
