SYCL :: Adapters/level_zero/interop-buffer.cpp failing on BMG Win
- Dominant language
- LLVM
- Stars
- 1.5k
- Forks
- 854
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 137
Description
### Describe the bug
SYCL :: Adapters/level_zero/interop-buffer.cpp sporadically failing on BMG Win
https://github.com/intel/llvm/actions/runs/27280305446/job/80579720703
Log is long, here is snippet
```
2026-06-10T14:28:45.3475333Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeDeviceGetRootDevice(hDevice, phRootDevice)
2026-06-10T14:28:45.3475367Z # |
2026-06-10T14:28:45.3475563Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeDeviceGetProperties(hDevice, pDeviceProperties)
2026-06-10T14:28:45.3475606Z # |
2026-06-10T14:28:45.3475830Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeDeviceGetRootDevice(hDevice, phRootDevice)
2026-06-10T14:28:45.3475866Z # |
2026-06-10T14:28:45.3475990Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeDeviceGetRootDevice(hDevice, phRootDevice)
2026-06-10T14:28:45.3476027Z # |
2026-06-10T14:28:45.3476124Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeKernelDestroy(hKernel)
2026-06-10T14:28:45.3476158Z # |
2026-06-10T14:28:45.3476292Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeKernelDestroy(hKernel)
2026-06-10T14:28:45.3476327Z # |
2026-06-10T14:28:45.3476419Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeKernelDestroy(hKernel)
2026-06-10T14:28:45.3476455Z # |
2026-06-10T14:28:45.3476578Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeModuleBuildLogDestroy(hModuleBuildLog)
2026-06-10T14:28:45.3476613Z # |
2026-06-10T14:28:45.3476888Z # | [2026-06-10 07:11:35.561] [thread-id: 7212] [trace] zeModuleDestroy(hModule)
2026-06-10T14:28:45.3476922Z # |
2026-06-10T14:28:45.3476972Z # `-----------------------------
2026-06-10T14:28:45.3477049Z # error: command failed with exit status: 0xc0000409
```
### To reproduce
1. Include a code snippet that is as short as possible
2. Specify the command which should be used to compile the program
3. Specify the command which should be used to launch the program
4. Indicate what is wrong and what was expected
### Environment
_No response_
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.