oneapi-src / oneapi-src/unified-runtime
[cuda] device_num.cpp sometimes failing on UR CI
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
I have not found examples of this failing on intel/llvm CI, but it is happening on UR CI for apparently unrelated PRs. see e.g.
- https://github.com/oneapi-src/unified-runtime/actions/runs/10767363770/job/29855526054?pr=2069
- https://github.com/oneapi-src/unified-runtime/actions/runs/10848734805/job/30107943832
- https://github.com/oneapi-src/unified-runtime/pull/1979
Maybe it is a general problem and it is just by chance I only see it happening on on UR ci. I note that l0 currently has the test xfail'd due to flaky failures. Or maybe it is something specific to UR ci.
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 with device_num.cpp and the linked UR CI runs, then inspect the l0 test that is currently marked xfail for flaky failures. Compare the failing CI context with the available examples to determine whether the problem is CI-specific or general. Done means the failure scope and cause are established and the relevant test or CI behavior is made reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100