-
Notifications
You must be signed in to change notification settings - Fork 769
[CI] Cancel previous run when new commit pushed #11941
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
Conversation
Last time I tried it, it didn't work and the whole CI just died. We also have an ongoing issue with Win CI, so I'm not going to merge it right now.
Is it about CUDA only or this PR in general? |
CUDA only. I can remove the CUDA part first for now. Windows/Linux pre-commit using concurrency tested in this PR. |
Ping.. I think this is general good for CI, may help with the windows CI too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change is good, but someone has to commit to keep closely monitoring CI after this is merged, possibly for a couple of days.
@intel/llvm-gatekeepers I think this is ready for merge. I will keep an eye in CI for days after it is merged. |
Merged. |
In case others are interested: 12-1 to 12-6, CI cancelled 20 of 154 run for windows, 15 of 154 runs for Linux. |
We've enabled the upstream community workflow in intel#12184 after discussion in intel#12085. It's been doing just fine, so the old can be removed now. We now start the build/tests before format checks are finished, but that shouldn't be a problem thanks to intel#11941.
In quite some PRs, we may need to push commits when the run is still in progress.
Currently we will run all the workflow to the end by default, which is somehow a waste of machine resource.
This PR use https://docs.github.com/en/actions/using-jobs/using-concurrency to group tests for Linux and Windows pre-commit tests, and cancel-in-progress if new commits are pushed.