> Using the new env var I was able to verify this, and this is in fact a highly > recurring error. Only this particular error has the Jira code.
My point is that when we write `#TODO: BEAM-1234` we mean that we expect that the failure will be fixed (or partially fixed) once BEAM-1234 is resolved. So if the test is failing for a different reason than is captured by BEAM-1234, then we should either use a generic Jira "Finish Python 3 porting for module xxx" or file a new Jira - if you think that underlying problem is worth tracking as an issue of its own and/or can be worked on in parallel. That said, are the Jira's you link in this PR accurate? [ Full content available at: https://github.com/apache/beam/pull/6590 ] This message was relayed via gitbox.apache.org for [email protected]
