[
https://issues.apache.org/jira/browse/BEAM-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954083#comment-15954083
]
Mark Liu commented on BEAM-1823:
--------------------------------
nose capture logs but not print them when using mutiprocess and interrupted by
TimedOutException. Created an issue on nose side:
https://github.com/nose-devs/nose/issues/1044
A work around solution is to print job id/metrics to std out with "-s" flag
(http://nose.readthedocs.io/en/latest/man.html#cmdoption-s).
> 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)
