oneapi-src / oneapi-src/unified-runtime
CI testing for UR_L0_CMD_BUFFER_USE_IMMEDIATE_APPEND_PATH
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
Merged PR https://github.com/oneapi-src/unified-runtime/pull/1975 added a new code path to the L0 command-buffer adapter when a device supports the zeCommandListImmediateAppendCommandListsExp experimental extension. Additional user control of code path selection is provided via the UR_L0_CMD_BUFFER_USE_IMMEDIATE_APPEND_PATH environment variable, which can force the path to be taken or not by the user.
As discussed in PR review comment thread https://github.com/oneapi-src/unified-runtime/pull/1975#discussion_r1848307360 we should have CI testing of both code paths enforced through use of the environment variable, as the default code path taken will vary depending on device/L0-driver.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading merged PR 1975 and the linked review discussion to find the L0 command-buffer adapter tests and CI configuration. Use UR_L0_CMD_BUFFER_USE_IMMEDIATE_APPEND_PATH to exercise both forced path selections, and consider the work done when CI reliably tests both code paths regardless of device or Level Zero driver defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100