beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet Altay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1793) Frequent python post commit errors
Date Tue, 28 Mar 2017 01:39:41 GMT

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

Ahmet Altay commented on BEAM-1793:
-----------------------------------

Another error after the change:
https://builds.apache.org/job/beam_PostCommit_Python_Verify/1644/consoleFull

Is there a way to verify that it ran one of the pinned nodes?

> Frequent python post commit errors
> ----------------------------------
>
>                 Key: BEAM-1793
>                 URL: https://issues.apache.org/jira/browse/BEAM-1793
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py
>            Reporter: Ahmet Altay
>            Assignee: Sourabh Bajaj
>            Priority: Critical
>
> 1. Failed because virtualenv was already installed. And postcommit script made a wrong
assumption about its location.
> https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/1499/consoleFull
> 2. Failed because a really old version of pip is installed:
> https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/1585/consoleFull
> (Also #1586 and #1597)
> 3. Failed because a file was already in the cache and pip did not want to override it,
even though this is not usually a problem:
> https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/1596/consoleFull
> (Might be related: https://issues.apache.org/jira/browse/BEAM-1788)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message