expert_cache_segmented_test fails on HIP builds instead of skipping (--vram-elastic is CUDA-only)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
Research direction
Find the expert_cache_segmented_test implementation and compare its unsupported-backend handling with other backend-specific tests that return 77. Run the test on a HIP build, then verify it skips successfully while the CUDA behavior remains unchanged.
Written by the indexing model from the issue text.
Description
On HIP builds, expert_cache_segmented_test fails instead of skipping:
FAIL open ExpertCache: --vram-elastic (a segmented expert cache) is CUDA-only for now
CMakeLists.txt already registers it with SKIP_RETURN_CODE 77, so the fix is for the test to return 77 when it is built without CUDA (or when ExpertCache reports the segmented mode unsupported), the same way other backend-specific tests skip. #918 lists it as one of the "known" HIP ctest failures, so every AMD ctest run currently shows one failure that isn't a bug.
Seen on an R9700 (gfx1201): ctest 90/95. The other failures were ple_parity, expert_parity and pool_test (they need model fixtures) and hip_q2_zero (filed separately).
Environment: Strata v0.1.40.3 (d5ea713), Linux (Ubuntu 24.04), AMD Radeon AI PRO R9700 (gfx1201, 32 GB), Ryzen 9 9900X, TheRock ROCm 7.10.0a20251120 (gfx120X-all wheels, setup's default), built by ./setup.sh --backend hip, then cmake -DSTRATA_BUILD_TESTS=ON + ctest --test-dir build-hip.
- Dominant language
- C++
- Stars
- 11.6k
- Forks
- 1k
- Avg merge
- 7h 46m
- Merged PRs (30d)
- 30
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Niko1221/Strata
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
EsotericSoftware/spine-runtimes#3186 ·
-
An empty line splits a signature where an ordinary comment is right above an argument's HaddockOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mrkkrp/tilia#213 · 1 comment ·
Maintainers usually reply within 1 day
-
Round video messages start gray and blocky with libx264: encoder is configured for 1,000,000 fpsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
telegramdesktop/tdesktop#31422 ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 5 days