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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:04 UTC

[jira] [Updated] (BEAM-3483) Introduce VirtualEnv for performance tests on Jenkins

     [ https://issues.apache.org/jira/browse/BEAM-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-3483:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Introduce VirtualEnv for performance tests on Jenkins
> -----------------------------------------------------
>
>                 Key: BEAM-3483
>                 URL: https://issues.apache.org/jira/browse/BEAM-3483
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Dariusz Aniszewski
>            Priority: P3
>
> Currently all performance tests are using python environment belonging to {{jenkins}} user. This started to be a problem when more that one test run at the same time on the same jenkins worker. In case of different packages, both jobs are altering the same environment and conflicting with each other.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)