test: skip upstream-flaky snap/runtime cases#2099
Merged
Merged
Conversation
The unofficial-builds musl channel lists a Node release in index.json as soon as its directory is created, before every architecture's binary is built. Resolving the "latest" alias can then pick a version whose linux-*-musl tarball is not published yet, so the download fails with HashNotFound (seen with node-v26.5.0-linux-x64-musl.tar.gz). Skip the two cases that exercise --node latest on musl: the runtime unit test test_download_runtime_for_project_with_latest_alias_in_node_version and the snap-tests-global command-env-install-version-alias fixture. Official nodejs.org releases are atomic, so glibc, darwin, and windows keep full coverage.
✅ Deploy Preview for viteplus-preview canceled.
|
Member
Author
How to use the Graphite Merge QueueAdd the label auto-merge to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
wan9chi
approved these changes
Jul 8, 2026
vp create astro --template basics scaffolds an astro dependency pinned to whatever the create-astro template currently references, which between astro releases is the next unpublished version (astro@^7.0.7 while 7.0.6 is the latest published). The following vp install then fails with ERR_PNPM_NO_MATCHING_VERSION on every platform. Skip the whole case until the create flow no longer depends on an unpublished template pin; the vp migrate astro shim cases still cover the shim itself.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Skips three CI cases that fail on transient upstream conditions, not on code in this repo.
Node
latestalias on muslunofficial-builds.nodejs.org lists a Node release in index.json as soon as its directory is created, before every architecture's binary is built. Resolving the
latestalias can pick a version whose linux-*-musl tarball is not published yet, so the download fails with HashNotFound (seen with node-v26.5.0-linux-x64-musl.tar.gz). Official nodejs.org releases are atomic, so glibc, darwin, and windows keep full coverage.test_download_runtime_for_project_with_latest_alias_in_node_version: skipped on muslcommand-env-install-version-alias: skipped on muslastro create shim
vp create astro --template basicsscaffolds an astro dependency pinned to the create-astro template's current reference, which between releases is the next unpublished version (astro@^7.0.7 while 7.0.6 is latest). The followingvp installthen fails with ERR_PNPM_NO_MATCHING_VERSION on every platform.create-framework-shim-astro: skipped (the vp migrate astro shim cases still cover the shim itself)