test(e2e): remove uv-deps-650's crossbuild sub-case - #1414
Conversation
This sub-case (image layers for amd64/arm64 + pyc/toolchain checks) is superseded by the dedicated e2e/crossbuild workspace arriving with the cross-compilation PR, which covers the same ground per PEP 517 backend with real QEMU execution. Removing it ahead of that PR keeps duplicate coverage out and trims the uv_deps_650 hub back to three projects. The uv-gazelle-778 manifest regenerates accordingly.
✨ Aspect Workflows Tasks📅 Tue Aug 11 05:55:05 UTC 2026 ✅ 42 successful tasks
⏱ Last updated Tue Aug 11 06:01:44 UTC 2026 · 📊 GitHub API quota 1,288/15,000 (9% used, resets in 22m) |
py_binary startup benchmark
sys.path quality
Bazel analysis benchmark
|
|
Can this not move to |
Removes the
crossbuildsub-case frome2e/cases/uv-deps-650(amd64/arm64 image-layer snapshots, pyc and exec-toolchain checks, ~4300 lines). It is superseded by the dedicatede2e/crossbuildworkspace arriving with #1363, which covers the same ground per PEP 517 backend with real QEMU execution and per-arch structural checks.Landing the removal ahead of #1363:
e2e/casesfootprint to only feature-coupled editspypi_uv_deps_650hub back to three projects (theuv-gazelle-778manifest regenerates accordingly)Pure deletion plus the two mechanical follow-ups — nothing on
mainreferences the removed targets (verified://:snapshots_*_testpoints ate2e/casesroot snapshots, and the only other "crossbuild" match is the unrelatedwindows-crossbuild-837). Fulle2e/casessuite green locally under--lockfile_mode=error.