[ 
https://issues.apache.org/jira/browse/BEAM-1817?focusedWorklogId=90094&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-90094
 ]

ASF GitHub Bot logged work on BEAM-1817:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Apr/18 18:08
            Start Date: 11/Apr/18 18:08
    Worklog Time Spent: 10m 
      Work Description: alanmyrvold commented on issue #4987: [BEAM-1817] 
Remove build machine pinning for python postcommit verify.
URL: https://github.com/apache/beam/pull/4987#issuecomment-380544985
 
 
   I tried unpinning the python validatescontainer and it failed when run on 
beam8. x86_64-linux-gnu-gcc: error: src/python/grpcio/grpc/_cython/cygrpc.c: No 
such file or directory
   
   
https://builds.apache.org/view/A-D/view/Beam/job/beam_PostCommit_Python_ValidatesContainer_Dataflow/100/console

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 90094)
    Time Spent: 50m  (was: 40m)

> Python environment is different on some nodes
> ---------------------------------------------
>
>                 Key: BEAM-1817
>                 URL: https://issues.apache.org/jira/browse/BEAM-1817
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core, testing
>            Reporter: Sourabh Bajaj
>            Assignee: Jason Kuster
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> We've pined the python post commits to specific nodes as pip in some of the 
> new nodes seems to be installed differently from the ones before.
> https://github.com/apache/beam/pull/2308/files
> Please remove the changes in above PR once this is resolved.



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

Reply via email to