You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Udi Meiri (JIRA)" <ji...@apache.org> on 2018/05/11 22:28:00 UTC

[jira] [Commented] (BEAM-3395) Python postcommit always runs on beam3

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

Udi Meiri commented on BEAM-3395:
---------------------------------

Fixed by [~pabloem] in https://github.com/apache/beam/pull/5214/files

> Python postcommit always runs on beam3
> --------------------------------------
>
>                 Key: BEAM-3395
>                 URL: https://issues.apache.org/jira/browse/BEAM-3395
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Udi Meiri
>            Assignee: Udi Meiri
>            Priority: Minor
>             Fix For: Not applicable
>
>
> In https://issues.apache.org/jira/projects/BEAM/issues/BEAM-1793, there was a change that set the list of allowed nodes and a default node. I believe that this change made postcommits always run on beam3.
> Evidence:
> https://builds.apache.org/job/beam_PostCommit_Python_Verify/buildTimeTrend
> https://builds.apache.org/job/beam_PostCommit_Python_ValidatesRunner_Dataflow/buildTimeTrend



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)