-
Notifications
You must be signed in to change notification settings - Fork 768
[CI] Fix sycl-rel-nightly.yml #16560
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
The workflow was introduced with errors. Fix them and also turn off the pre-commit for changes in this workflow.
@@ -50,9 +50,6 @@ on: | |||
description: 'Artifacts retention period' | |||
type: string | |||
default: 3 | |||
ref: |
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.
Note for reviewers: I added these changes (and one below) previously, but they are not needed actually, so removing them.
Example of run: https://github.com/intel/llvm/actions/runs/12674915797 |
post-commit failure: #16568 |
That input parameter was introduced to `sycl-windows-build.yml` in intel#16560 but it's unclear why. Note that linux version has had it for quite some time, but we started unsetting it explicitly in intel#10720. The reason we had it for Linux in the first place is because `GITHUB_SHA` pointed to the PR's source branch for the `pull_request_target` trigger that we used at that time. With switching to `pull_request` trigger it became unnecessary as `GITHUB_SHA` points to the merge commit already. This change should fix current race condition when a post-commit CI job can test change landed after the current commit if there is a delay with runner allocation.
…16757) That input parameter was introduced to `sycl-windows-build.yml` in #16560 but it's unclear why. Note that linux version has had it for quite some time, but we started unsetting it explicitly in #10720. The reason we had it for Linux in the first place is because `GITHUB_SHA` pointed to the PR's source branch for the `pull_request_target` trigger that we used at that time. With switching to `pull_request` trigger it became unnecessary as `GITHUB_SHA` points to the merge commit already. This change should fix current race condition when a post-commit CI job can test change landed after the current commit if there is a delay with runner allocation.
The workflow was introduced with errors. Fix them and also turn off the pre-commit for changes in this workflow.