You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Mark Liu (JIRA)" <ji...@apache.org> on 2017/03/30 00:53:42 UTC

[jira] [Commented] (BEAM-1823) TimedOutException in postcommit

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

Mark Liu commented on BEAM-1823:
--------------------------------

We set ValidatesRunner test timeout here: https://github.com/apache/beam/blob/master/sdks/python/run_postcommit.sh#L81

Currently it's 600s. So I think this is an special case that job exceeds time limit but succeeds in the end. From my observation, a ValidatesRunner generally takes about 4~5mins to finish. But we can increase the timeout considering bakend occasionally slow down.

Log is controlled by nose. Need further investigate to see if full console log can print in this case. Also having job_id printed in ValidatesRunner test (BEAM-1728) definitely helps for debugging.

> 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)