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

only run one test suite per PR #4266

Merged
merged 1 commit into from
Feb 15, 2023
Merged

only run one test suite per PR #4266

merged 1 commit into from
Feb 15, 2023

Conversation

ahnitz
Copy link
Member

@ahnitz ahnitz commented Feb 15, 2023

Taking the advice here

https://stackoverflow.com/questions/66335225/how-to-cancel-previous-runs-in-the-pr-when-you-push-new-commitsupdate-the-curre/67939898#67939898

At the moment, the test suite runs for each commit. That means if you identify a problem and push a new commit to a branch, you'll have to wait for the previous commit to finish its tests and free up resources to run. I don't think in general we want that behavior and it would tend to bottleneck running the test suite with actively developed PRs.

This change to our runs of the test suite would mean that only a single set is run per PR (or tag / branch) at a time. The previous workflows from the prior commit are cancelled when a new commit appears.

@ahnitz ahnitz requested a review from spxiwh February 15, 2023 15:08
Copy link
Contributor

@spxiwh spxiwh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A nice feature to add!

@ahnitz ahnitz merged commit c0920d5 into gwastro:master Feb 15, 2023
acorreia61201 pushed a commit to acorreia61201/pycbc that referenced this pull request Apr 4, 2024
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 this pull request may close these issues.

2 participants