[TRACKER] CI Test Failures Needing attention
Open
Nobody has claimed this yet.
bug
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
This is a tracker issue for CI test failures, mostly from flaky tests, that need attention. We should strive to root cause and fix the issues, rather than skipping tests or adjusting thresholds without understanding why the test is failing.
- https://github.com/NVIDIA/cuvs/issues/2406
- https://github.com/rapidsai/cuvs/issues/2094
- https://github.com/rapidsai/cuvs/issues/2100
- https://github.com/rapidsai/cuvs/issues/2093
- https://github.com/NVIDIA/cuvs/issues/2137
- https://github.com/NVIDIA/cuvs/issues/2588
- https://github.com/NVIDIA/cuvs/issues/2549
- https://github.com/NVIDIA/cuvs/issues/2551
- https://github.com/NVIDIA/cuvs/issues/2522
- https://github.com/NVIDIA/cuvs/issues/2550
- https://github.com/NVIDIA/cuvs/issues/2602
Todo:
After release/26.10 reenable AnnNNDescentTestUI8_U32.
Contributor guide
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 reviewing the unchecked linked issues and their CI failure details, especially the listed test-failure reports. Work through each failure to identify and fix its root cause rather than skipping tests or changing thresholds; the tracker is complete when the failures are resolved and AnnNNDescentTestUI8_U32 is re-enabled after release/26.10.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100