Skip to content

[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

Merged
merged 1 commit into from
Jan 9, 2025
Merged

[CI] Fix sycl-rel-nightly.yml #16560

merged 1 commit into from
Jan 9, 2025

Conversation

KornevNikita
Copy link
Contributor

The workflow was introduced with errors. Fix them and also turn off the pre-commit for changes in this workflow.

The workflow was introduced with errors. Fix them and also turn off the
pre-commit for changes in this workflow.
@KornevNikita KornevNikita requested a review from a team as a code owner January 8, 2025 18:11
@@ -50,9 +50,6 @@ on:
description: 'Artifacts retention period'
type: string
default: 3
ref:
Copy link
Contributor Author

@KornevNikita KornevNikita Jan 8, 2025

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.

@KornevNikita
Copy link
Contributor Author

Example of run: https://github.com/intel/llvm/actions/runs/12674915797
Fails in this run are expected, we need to cherry-pick some patches.

@KornevNikita
Copy link
Contributor Author

post-commit failure: #16568
@intel/llvm-gatekeepers could you please merge

@steffenlarsen steffenlarsen merged commit a5f83c2 into sycl Jan 9, 2025
32 of 40 checks passed
@KornevNikita KornevNikita deleted the fix-nightly-rel branch January 9, 2025 11:34
aelovikov-intel added a commit to aelovikov-intel/llvm that referenced this pull request Jan 23, 2025
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.
aelovikov-intel added a commit that referenced this pull request Jan 23, 2025
…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.
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.

3 participants