[CI] Add LTS driver job to nightly - #22935
Merged
Merged
Conversation
Signed-off-by: Nick Sarnie <nick.sarnie@intel.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
KornevNikita
approved these changes
Aug 13, 2026
Contributor
Author
|
thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use the new LTS docker container in the nightly to lock down we didn't completely break support on the LTS driver, which we need to support.
Note this runs on a runner with a special label,
pvc_lts, as we also need the LTS kernel driver for true verification. This runner is only used for this job (I took a machine which had 2 PVC cards and put 1 of them into a VM with the LTS kernel driver, the existing runner for this machine only used 1 PVC card anyway, so there is no slowdown)A major difference with normal E2E jobs is we don't run all/most tests, actually most tests fail. I think (hope?) this is expected because it's fine if we require a new driver for new SYCL features and probably most tests are for new features, the main idea is to lock down we didn't universally enable some new SPIR-V extension or something that completely breaks everything.
I asked an LLM to pick 5 tests to maximize coverage out of the ~270 passing tests, and made a new file in
devopsthat lists them. This file will be read by the job and end up as theLIT_FILTERenvvar.I didn't want to enable/disable tests directly in E2E code as we'd have to either mark thousands of failing tests as
UNSUPPORTEDor make this configUNSUPPORTEDby default and removeUNSUPPORTEDfrom hundreds of passing tests usinglit.local.cfg, seems much more trouble than it's worth.I went with a separate file in
devopsinstead hardcoding it in the job for better extendability and understandability.Example CI run: https://github.com/intel/llvm/actions/runs/31633290719/job/94240857548