-
Notifications
You must be signed in to change notification settings - Fork 115
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] Add "loader" support to conformance testing #2082
Conversation
7f5f4dc
to
37b9c8a
Compare
37b9c8a
to
b311697
Compare
765d74d
to
1a590df
Compare
43feaa2
to
6b30976
Compare
23ec456
to
c26d47e
Compare
c26d47e
to
0193d8e
Compare
1c51ebc
to
5901769
Compare
d147c8f
to
1503e67
Compare
fd9b9ef
to
74eaf70
Compare
6f75bec
to
29f5904
Compare
.github/workflows/cmake.yml
Outdated
@@ -187,6 +187,24 @@ jobs: | |||
adapter_name: NATIVE_CPU | |||
runner_name: NATIVE_CPU | |||
|
|||
# Native CPU jobs are here to force the loader to be used |
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.
Is there value in testing the loader with CUDA/HIP? It would use more CI resources but might catch more issues.
@@ -0,0 +1,3 @@ | |||
# Note: This file is only for use with cts_exe.py |
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.
I might be wrong but shouldn't this note be true for all match files, and if so, I don't think we need to add this note.
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.
There are two programs now that handle match files; the older matching logic and cts_exe.py. When I updated the files, I did so in a way incompatible with the old match checker thing. Figured I'd add a note calling that out.
Although, happy to remove it now that we've transitioned to using cts_exe.py.
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.
Ah okay make sense, I think it is better to keep it for now to avoid confusion then with the old matching logic. might be worth also calling out explicitly that this is incompatible with the old matching system. (doesn't have strong opinions about this)
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.
#2285 Decided to go hard in the other direction. Drop support for the older matching logic and make our testing files look neater. Not sure how popular a change this will be though.
29f5904
to
60d53ec
Compare
This expands our CI to test the loader; the dispatcher that is used when multiple adapters are availabe. The old "run on hardware" jobs should behave the same (they have the loader tests disabled), but there are new "combined" jobs with OpenCL/Level Zero + Native CPU. Closes: oneapi-src#2081
60d53ec
to
0b96866
Compare
Merging without LLVM change, as this only affects our testing. |
This expands our CI to test the loader; the dispatcher that is
used when multiple adapters are available.
The old "run on hardware" jobs should behave the same (they have
the loader tests disabled), but there are new "combined" jobs
with OpenCL/Level Zero + Native CPU.
Closes: #2081