[CI] Move SPIRV-backend testing to post-commit #19669
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
aelovikov-intel
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
aelovikov-intel
force-pushed
the
move-spirv-backend-e2e
branch
from
490abfa to
20ace65
Compare
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
force-pushed
the
move-spirv-backend-e2e
branch
from
20ace65 to
0ee77dc
Compare
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
aelovikov-intel
force-pushed
the
move-spirv-backend-e2e
branch
from
0ee77dc to
fac3809
Compare
aelovikov-intel
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
aelovikov-intel
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
aelovikov-intel
force-pushed
the
move-spirv-backend-e2e
branch
from
fac3809 to
0bc6a7b
Compare
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
commented
Aug 1, 2025
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
force-pushed
the
move-spirv-backend-e2e
branch
from
a5f090e to
bcc1e51
Compare
aelovikov-intel
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
sarnex
approved these changes
Aug 1, 2025
againull
approved these changes
Aug 4, 2025
|
Yeah sorry I'm not really a runtime team member so I usually re-add the team to reviews whenever my review is used for runtime, I'm in the group for CI/test reasons |
No worries, that's my bad |
|
@reble , @intel/sycl-graphs-reviewers , ping. The change in the graphs tests is minimal and shouldn't take more than a few minutes to review. |
adamfidel
approved these changes
Aug 5, 2025
|
Windows failure is #19660, unrelated. |
uditagarwal97
added a commit
that referenced
this pull request
Oct 20, 2025
Fixes E2E test failure in `SeperateCompile/test.cpp` in sycl-rel 6.3 ABI testing(https://github.com/intel/llvm/actions/runs/18599730732/job/53035028308#step:27:2964) The test failure is because of lit using system-installed `sycl-post-link` instead of the newly built one. This PR forces lit to find and use tools from `<compiler build>/bin` directory. These changes are already in `sycl` branch (brought in by #19669)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Development happens mostly upstream, so there is no need to have that in pre-commit, post-commit should be enough.
Before this PR, when running E2E tests in "in-tree" mode (as opposite to a standalone e2e tests cmake invocation), some utilities (e.g.
llvm-ar) were only searched for inPATHthat didn't contain freshly built toolchain. Our pre-commit used a container image with last successful "Nightly" toolchain installed, so those were picked up from there. Post-commit uses GNU Compiler instead of Clang, so these utilities aren't available inPATH.This PR modifies
lit.cfg.pysuch that we search for those utilities in the newly built toolchain first (still not modifyingPATHwhich seems to be the approach taken in LIT). That also ensures thatopencl-aotfeature is available when running E2E tests inbuild-onlymode in Post-commit's build job.