[CI] CUTILE_SMOKE_TEST GB300 failed
Maintainers usually reply within 1 day
@viclafargue is already working on this.
Since Sep 28, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp, github-actions
- Domain
- ci-cd, testing-qa
Research direction
Start with tests/detail/jit_lto/cutile_smoke.cu, especially the failing CutileSmoke.LaunchesCompatibleCubin test, and inspect the linked GitHub Actions job on a GB300 runner. Reproduce CUTILE_SMOKE_TEST in the affected release/26.10 or main nightly workflow; done means both smoke tests pass on GB300 runners.
Written by the indexing model from the issue text.
Description
release/26.10 and main Nighlies that use GB300 runners are failing with:
https://github.com/NVIDIA/cuvs/actions/runs/34517645748/job/103007042888#step:12:3119
5/38 Test #5: CUTILE_SMOKE_TEST ..........................***Failed 0.13 sec
'./../../..//bin/gtests/libcuvs/CUTILE_SMOKE_TEST'
Running main() from /tmp/conda-bld-output/bld/rattler-build_libcuvs-headers/work/cpp/build/_deps/gtest-src/googletest/src/gtest_main.cc
[==========] Running 2 tests from 1 test suite.
[----------] Global test environment set-up.
[----------] 2 tests from CutileSmoke
[ RUN ] CutileSmoke.ResolvesEveryEmbeddedArchitecture
[ OK ] CutileSmoke.ResolvesEveryEmbeddedArchitecture (0 ms)
[ RUN ] CutileSmoke.LaunchesCompatibleCubin
/tmp/conda-bld-output/bld/rattler-build_libcuvs-headers/work/cpp/tests/detail/jit_lto/cutile_smoke.cu:86: Failure
Expected: (launcher) != (nullptr), actual: (nullptr) vs (nullptr)
cc @divyegala
- Dominant language
- Cuda
- Stars
- 863
- Forks
- 242
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 81
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from NVIDIA/cuvs
-
[BUG] cuVS Bench Faiss CAGRA b_ratio reads the wrong JSON keyPossibly taken @arcusbuilds claimed this 7 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
doc
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
faiss improvement
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
ci-install-db-tools stall-case tests flake: stalled apt-get can be killed before it logs its callOpeneffort:low model:light plan planner:opus-5-5 tests
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
component/test-automation work/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bcgov/bc-wallet-mobile#4845 ·
Maintainers usually reply within 1 day
-
first
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AcademySoftwareFoundation/rmtc#54 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stac-utils/stac-fastapi-elasticsearch-opensearch#932 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
maplibre/maplibre-native-ffi#792 ·
Maintainers usually reply within 1 day