[jira] [Commented] (BEAM-1793) Frequent python post commit errors

2017-03-28 Thread Ahmet Altay (JIRA)

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

Ahmet Altay commented on BEAM-1793:
---

typo: https://issues.apache.org/jira/browse/BEAM-1817 is the tracking issue for 
the real fix.

> 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
> Fix For: First stable release
>
>
> 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)


[jira] [Commented] (BEAM-1793) Frequent python post commit errors

2017-03-28 Thread Ahmet Altay (JIRA)

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

Ahmet Altay commented on BEAM-1793:
---

>From this page: 
>https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/

It looks like the config change was applied at #1648, we can ignore my comment 
above. I will close this issue.

https://issues.apache.org/jira/browse/BEAM-1813 is the tracking issue for the 
real fix. 

> 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
> Fix For: First stable release
>
>
> 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)


[jira] [Commented] (BEAM-1793) Frequent python post commit errors

2017-03-27 Thread Ahmet Altay (JIRA)

[ 
https://issues.apache.org/jira/browse/BEAM-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


[jira] [Commented] (BEAM-1793) Frequent python post commit errors

2017-03-27 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on BEAM-1793:
--

Github user asfgit closed the pull request at:

https://github.com/apache/beam/pull/2308


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