[jira] [Commented] (BEAM-3480) Jenkins IOIT jobs unstable

2018-01-29 Thread Chamikara Jayalath (JIRA)

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

Chamikara Jayalath commented on BEAM-3480:
--

Alan pointed out following flag.
https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/blob/master/perfkitbenchmarker/temp_dir.py#L35

Can we try setting a new temp directory in case some of the executors have a 
'/tmp/perfkitbenchmarker' with bad permissions ?

> Jenkins IOIT jobs unstable
> --
>
> Key: BEAM-3480
> URL: https://issues.apache.org/jira/browse/BEAM-3480
> Project: Beam
>  Issue Type: Bug
>  Components: testing
>Reporter: Dariusz Aniszewski
>Assignee: Jason Kuster
>Priority: Major
>
> From some time, Jenkins jobs running performance tests via PerfKit, are 
> failing due to permission issues while creating temporary directory, ie:
> {noformat}
> OSError: [Errno 13] Permission denied: '/tmp/perfkitbenchmarker/runs/cf0322bf'
> {noformat}
>  
> It is possible that this is related to worker's configurations. I noticed 
> that there are few workers on which tests are passing, and few that are 
> constantly failing. See list here:
> [https://docs.google.com/spreadsheets/d/1rvJjrR3BC9hwvpfWOszDoGRA7hr1Vke7PbitwQEKk0Q/edit#gid=0]
>  



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


[jira] [Commented] (BEAM-3480) Jenkins IOIT jobs unstable

2018-01-29 Thread JIRA

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

Łukasz Gajowy commented on BEAM-3480:
-

Solving this issue is crucial for running IOIT tests on Jenkins. Is there any 
progress with this issue, maybe ([~alanmyrvold], [~jasonkuster])?

> Jenkins IOIT jobs unstable
> --
>
> Key: BEAM-3480
> URL: https://issues.apache.org/jira/browse/BEAM-3480
> Project: Beam
>  Issue Type: Bug
>  Components: testing
>Reporter: Dariusz Aniszewski
>Assignee: Jason Kuster
>Priority: Major
>
> From some time, Jenkins jobs running performance tests via PerfKit, are 
> failing due to permission issues while creating temporary directory, ie:
> {noformat}
> OSError: [Errno 13] Permission denied: '/tmp/perfkitbenchmarker/runs/cf0322bf'
> {noformat}
>  
> It is possible that this is related to worker's configurations. I noticed 
> that there are few workers on which tests are passing, and few that are 
> constantly failing. See list here:
> [https://docs.google.com/spreadsheets/d/1rvJjrR3BC9hwvpfWOszDoGRA7hr1Vke7PbitwQEKk0Q/edit#gid=0]
>  



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


[jira] [Commented] (BEAM-3480) Jenkins IOIT jobs unstable

2018-01-19 Thread Chamikara Jayalath (JIRA)

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

Chamikara Jayalath commented on BEAM-3480:
--

cc: [~alanmyrvold]

> Jenkins IOIT jobs unstable
> --
>
> Key: BEAM-3480
> URL: https://issues.apache.org/jira/browse/BEAM-3480
> Project: Beam
>  Issue Type: Bug
>  Components: testing
>Reporter: Dariusz Aniszewski
>Assignee: Jason Kuster
>Priority: Major
>
> From some time, Jenkins jobs running performance tests via PerfKit, are 
> failing due to permission issues while creating temporary directory, ie:
> {noformat}
> OSError: [Errno 13] Permission denied: '/tmp/perfkitbenchmarker/runs/cf0322bf'
> {noformat}
>  
> It is possible that this is related to worker's configurations. I noticed 
> that there are few workers on which tests are passing, and few that are 
> constantly failing. See list here:
> [https://docs.google.com/spreadsheets/d/1rvJjrR3BC9hwvpfWOszDoGRA7hr1Vke7PbitwQEKk0Q/edit#gid=0]
>  



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


[jira] [Commented] (BEAM-3480) Jenkins IOIT jobs unstable

2018-01-15 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on BEAM-3480:
--

DariuszAniszewski opened a new pull request #4416: [BEAM-3480] Temporarily run 
PerfKit jobs on Jenkins on subset of workers
URL: https://github.com/apache/beam/pull/4416
 
 
   Follow this checklist to help us incorporate your contribution quickly and 
easily:
   
- [x] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the 
change (usually before you start working on it).  Trivial changes like typos do 
not require a JIRA issue.  Your pull request should address just this issue, 
without pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line 
and body.
- [x] Format the pull request title like `[BEAM-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA 
issue.
- [x] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will be performed on your pull request automatically.
- [x] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   ---
   


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


> Jenkins IOIT jobs unstable
> --
>
> Key: BEAM-3480
> URL: https://issues.apache.org/jira/browse/BEAM-3480
> Project: Beam
>  Issue Type: Bug
>  Components: testing
>Reporter: Dariusz Aniszewski
>Assignee: Jason Kuster
>Priority: Major
>
> From some time, Jenkins jobs running performance tests via PerfKit, are 
> failing due to permission issues while creating temporary directory, ie:
> {noformat}
> OSError: [Errno 13] Permission denied: '/tmp/perfkitbenchmarker/runs/cf0322bf'
> {noformat}
>  
> It is possible that this is related to worker's configurations. I noticed 
> that there are few workers on which tests are passing, and few that are 
> constantly failing. See list here:
> [https://docs.google.com/spreadsheets/d/1rvJjrR3BC9hwvpfWOszDoGRA7hr1Vke7PbitwQEKk0Q/edit#gid=0]
>  



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