-
Notifications
You must be signed in to change notification settings - Fork 738
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
[CI] Enable check-sycl-unittests in CI #12858
Changes from 16 commits
2294de7
3c94b43
3428ee3
f7c1fa5
e7e93e4
4141f31
cdd8d73
bbe4266
520d645
c28e980
1015f8f
ae7c754
cfab312
691616b
001d567
85f388c
6c4e961
c6b3e3b
4f25c62
e9d598a
4663ead
219bbfe
54e5c60
c0aa422
c50a6fc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -97,6 +97,10 @@ jobs: | |
shell: bash | ||
run: | | ||
cmake --build build --target sycl-toolchain | ||
- name: Setup SYCL toolchain | ||
run: | | ||
# Need this for check-sycl-unittests. | ||
echo "PATH=$env:GITHUB_WORKSPACE\\build\\bin;$env:PATH" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why here and not in cmake? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I did tried moving this to the CMake file, but that doesn't seem to help. Setting PATH in AddSYCLUnitTest.cmake file seems to reflect in the "cmake -E" command but the updated PATH is not visible when the unit tests are actually executed. My hypothesis is CMake is spawning two subprocess, one for compiling (cmake -E command) and another for running the unit tests. Updating PATH in the cmake file seems to affect only the former subprocess. Nevertheless, this problem of check-sycl-unittests using old sycl library is only affecting CI, so just adding a workaround in the workflow file seems to suffice for the time being. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I don't think it's true. It would be the same locally. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not able to reproduce this locally, both on Linux and Windows (with and without u4win). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually, you are right - I'm now able to reproduce it locally. This time, I kept two |
||
- name: check-llvm | ||
if: always() && !cancelled() && contains(inputs.changes, 'llvm') | ||
run: | | ||
|
@@ -109,6 +113,10 @@ jobs: | |
if: always() && !cancelled() && contains(inputs.changes, 'sycl') | ||
run: | | ||
cmake --build build --target check-sycl | ||
- name: check-sycl-unittests | ||
if: always() && !cancelled() && contains(inputs.changes, 'sycl') | ||
run: | | ||
cmake --build build --target check-sycl-unittests | ||
- name: check-llvm-spirv | ||
if: always() && !cancelled() && contains(inputs.changes, 'llvm_spirv') | ||
run: | | ||
|
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.
This needs a comment explaining the issue and why we deal with it this way and what other alternatives were rejected.