Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add concurrency limits, to reduce the GitHub Actions usage #5073

Closed
pradyunsg opened this issue Apr 22, 2022 · 1 comment · Fixed by #5079
Closed

Add concurrency limits, to reduce the GitHub Actions usage #5073

pradyunsg opened this issue Apr 22, 2022 · 1 comment · Fixed by #5079
Assignees

Comments

@pradyunsg
Copy link
Member

pradyunsg commented Apr 22, 2022

Currently, pipenv's test suite is consuming a substantial portion of the GitHub Actions workers available to the PyPA as a whole, due to multiple concurrent runs on the same PR / multiple PR merges.

Adding a block like the following, to the top level of the CI pipeline would help alleviate some of this load.

concurrency:
  group: >-
    ${{ github.workflow }}-
    ${{ github.ref_type }}-
    ${{ github.event.pull_request.number || github.sha }}
  cancel-in-progress: true

In a similar vein, it could be beneficial to explore speeding up the test suite/CI runs if that is feasible, through the use of caches and RAM disks. :)

@oz123
Copy link
Contributor

oz123 commented Apr 24, 2022

The test suite is a real PITA. Hopefully, we can improve it.

@oz123 oz123 self-assigned this Apr 24, 2022
oz123 added a commit that referenced this issue Apr 24, 2022
matteius pushed a commit that referenced this issue Apr 24, 2022
oz123 added a commit that referenced this issue Apr 24, 2022
oz123 added a commit that referenced this issue Apr 24, 2022
oz123 added a commit that referenced this issue Apr 24, 2022
fraser-langton pushed a commit to fraser-langton/pipenv that referenced this issue Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants