Repository navigation
[CI] Pin the wheel-test torch to a shipped PG build - #4440
Conversation
test_installation.sh installs torch unpinned, so a fresh PyPI release (2.14.1) lands in the test env while the wheel only ships PG builds for EP_TORCH_VERSIONS (up to 2.14.0). mooncake.pg then looks for mooncake.pg_2_14_1, and all six test_pg_* modules fail at import on every PR (#4439). The wheel is already installed at that point, so enumerate the mooncake.pg_* modules it ships and install the newest matching torch. Wheels without PG builds (non-cuda) keep the previous unpinned behavior. Signed-off-by: Yufeng He <40085740+he-yufeng@users.noreply.github.com>
|
Status update: the end-to-end validation the description was waiting for is in. Both test-wheel-ubuntu legs pass on this PR (py312 in 20m58s, py310 in 6m22s), while the same job fails on every other open PR with Since this unblocks CI for the whole open queue, a review when someone has a moment would help. @Aionw you merged most of the recent CI fixes, maybe you have context on this one. |
|
Third day of repo-wide red from this gap: every open PR's test-wheel legs fail with the same missing pg_2_14_1 module (latest run 37178068463 this morning). This PR still passes both test-wheel legs end to end and the change is a one-line pin. If the pin direction looks right, merging it unblocks the whole queue; happy to adjust if a bounded torch range is preferred over a pin. |
scripts/test_installation.sh installed torch unpinned, so PyPI's latest (2.14.1) landed in the test venv while the wheel only ships PG builds for EP_TORCH_VERSIONS (up to 2.14.0); mooncake.pg then looked for mooncake.pg_2_14_1 and all test_pg_* modules failed at import. Enumerate the mooncake.pg_* modules the installed wheel ships and install the newest matching torch. Wheels without PG builds keep the previous unpinned behavior. Mirrors kvcache-ai#4440 (fixes kvcache-ai#4439) so this PR's test-wheel-ubuntu legs go green; drop on rebase once kvcache-ai#4440 lands.
|
I think getting #3673 merged is the ultimate fix. |
|
Agreed, #3673 is the real fix. This PR is deliberately only an interim pin: it touches nothing outside the wheel-test workflow, it can't conflict with the JIT rework, and it keeps the test-wheel legs meaningful for the other open PRs until #3673 lands (right now all of them fail at import on the missing pg_2_14_1 module). Once #3673 merges I'll close this. If you'd rather not take an interim pin at all, say so and I'll close it now; the lane just stays red until then. |
|
Agreed that #3673 is where this should end up. In the meantime the wheel job fails on every open PR: test_installation.sh installs an unpinned torch, which now resolves to 2.14.1, while the shipped wheels only carry PG builds up to 2.14.0, so all six test_pg_* modules die at import. That failure is currently noise on top of every PR's real signal. This pin just ties the test env to a torch the shipped PG actually covers, so CI reads clean until the JIT adapter removes the coupling. Once #3673 lands I can rebase this down to nothing or close it outright, whichever is cleaner. |
This reverts commit b079bfb.
Description
Fixes #4439.
The wheel test legs of CI are red on every PR right now.
scripts/test_installation.shinstalls torch unpinned, so PyPI's latest (2.14.1) lands in the test venv, while the wheel only ships PG builds forEP_TORCH_VERSIONS(currently up to 2.14.0).mooncake.pgthen looks formooncake.pg_2_14_1, and all sixtest_pg_*modules fail at import.The wheel is already installed a few lines earlier in the same script, so it now enumerates the
mooncake.pg_*modules the wheel ships and installs the newest matching torch. Wheels without PG builds (non-cuda variants, or any detection failure) keep the previous unpinned behavior, so the change cannot make a green run worse.Module
Type of Change
How Has This Been Tested?
Test commands:
Test results:
torch==2.14.0, the newest shipped variantpip install torch numpy|| truekeepsset -eintact, same fallbacktest-wheel-ubuntulegs, which should go green againChecklist
bash -n; no pre-commit hook covers it)AI Assistance Disclosure
Kimi Code drafted the change; verification steps above were actually run as described, and the submitter has reviewed every changed line.