[
https://issues.apache.org/jira/browse/BEAM-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954342#comment-15954342
]
Mark Liu commented on BEAM-1823:
--------------------------------
I'm okay with this trick before the issue is fixed in nosetest side, since
general test run with nose framework will remain the same.
One possible place I can think of to add is before
[test_dataflow_runner.wait_until_finish()|https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/dataflow/test_dataflow_runner.py#L33].
Since this is more Dataflow related issue, printing job_id in
test_dataflow_runner will not affect logs of other runners.
> TimedOutException in postcommit
> -------------------------------
>
> Key: BEAM-1823
> URL: https://issues.apache.org/jira/browse/BEAM-1823
> Project: Beam
> Issue Type: Bug
> Components: sdk-py
> Reporter: Ahmet Altay
> Assignee: Mark Liu
>
> Mark, do you know what this error means? Where is the timeout configured.
> https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/1657/console
> I _think_ this is one of the underlying Dataflow executions and it completed
> (although much slower than usual):
> https://pantheon.corp.google.com/dataflow/job/2017-03-28_14_25_21-13472017589125356257?project=apache-beam-testing&organizationId=433637338589
> It makes sense to time out the test but I want to know how it is configured.
> Also, is it possible to print out output logs for failed/timed out tests so
> that we can clearly associate tests with job executions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
