[CI] Add "loader" support to conformance testing #2082
Draft
+30
−5
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.
This expands our CI to test the loader; the dispatcher that is
used when multiple adapters are availabe.
Previously, the unit tests forced a specific adapter, via
UR_ADAPTERS_FORCE_LOAD
. Now an extra "loader" target is createdfor each test suite, which doesn't set that variable and allows
the loader to be used.
In addition, the test runner's adapter selection logic has been
rewritten to support a "--backend" variable, which allows you to
select a backend (OpenCL, Level Zero, etc.).
The platform selection has also been expanded to support
filtering by a backend to match that platform only on that backend
(e.g.
UR_CTS_ADAPTER_PLATFORM="opencl:Fictional Corp(R)"
).The old "run on hardware" jobs should behave the same (they have
the loader tests disabled), but there is a new
combined-opencl-level-zero
job that tests a build with bothOpenCL and Level Zero available.
Closes: #2081