[SYCL] Unittest QueueID.QueueCreationUSMOperations failed on Linux in CI
- Dominant language
- LLVM
- Stars
- 1.5k
- Forks
- 854
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 137
Description
### Describe the bug
This failure was observed while enabling check-sycl-unittests in CI: https://github.com/intel/llvm/actions/runs/8145615583/job/22262283285#step:9:1313
In file: sycl/unittests/xpti_trace/QueueIDCheck.cpp
```
2024-03-04T19:07:40.2972086Z [ RUN ] QueueID.QueueCreationUSMOperations
2024-03-04T19:07:40.2972466Z /__w/llvm/llvm/src/sycl/unittests/xpti_trace/QueueIDCheck.cpp:61: Failure
2024-03-04T19:07:40.2972814Z Value of: Message
2024-03-04T19:07:40.2973020Z Expected: has substring "task_begin:queue_id:22"
2024-03-04T19:07:40.2973288Z Actual: "task_begin:queue_id:16"
2024-03-04T19:07:40.2973441Z
2024-03-04T19:07:40.2973630Z /__w/llvm/llvm/src/sycl/unittests/xpti_trace/QueueIDCheck.cpp:64: Failure
2024-03-04T19:07:40.2973964Z Value of: Message
2024-03-04T19:07:40.2974169Z Expected: has substring "task_end:queue_id:22"
2024-03-04T19:07:40.2974429Z Actual: "task_end:queue_id:16"
2024-03-04T19:07:40.2974572Z
2024-03-04T19:07:40.2974753Z /__w/llvm/llvm/src/sycl/unittests/xpti_trace/QueueIDCheck.cpp:61: Failure
2024-03-04T19:07:40.2975085Z Value of: Message
2024-03-04T19:07:40.2975290Z Expected: has substring "task_begin:queue_id:22"
2024-03-04T19:07:40.2975550Z Actual: "task_begin:queue_id:16"
2024-03-04T19:07:40.2975703Z
2024-03-04T19:07:40.2975879Z /__w/llvm/llvm/src/sycl/unittests/xpti_trace/QueueIDCheck.cpp:64: Failure
2024-03-04T19:07:40.2976211Z Value of: Message
2024-03-04T19:07:40.2976413Z Expected: has substring "task_end:queue_id:22"
2024-03-04T19:07:40.2976667Z Actual: "task_end:queue_id:16"
2024-03-04T19:07:40.2976808Z
2024-03-04T19:07:40.2976943Z [ FAILED ] QueueID.QueueCreationUSMOperations (0 ms)
```
### To reproduce
Run check-sycl-unittest on latest intel/llvm (8d2d870247065a2a7). The failure should be reproducible on both CPU and GPU.
### Environment
OS: Linux
intel/llvm commit id: 8d2d870247065a2a7
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.