Repository navigation
tests(realpath): enable wasi integration tests - #15323
Open
eduardomourar wants to merge 1 commit into
Open
eduardomourar wants to merge 1 commit into
eduardomourar wants to merge 1 commit into
Conversation
sylvestre
reviewed
Oct 14, 2026
sylvestre
reviewed
Oct 14, 2026
eduardomourar
force-pushed
the
feat/wasi-realpath-tests
branch
2 times, most recently
from
October 14, 2026 20:11
bb07e10 to
e169d9f
Compare
eduardomourar
force-pushed
the
feat/wasi-realpath-tests
branch
from
October 14, 2026 21:01
45c0b9d to
03a399f
Compare
This branch has not been deployed
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
2 participants
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.
Enable
test_realpath::forwasm32-wasip1in CI, ignoring cases incompatible with the WASI sandbox: canonicalization resolves against the guest's virtual root rather than the host's absolute path, and symlinks created via symlink_file/symlink_dir store an absolute host path as their target, which resolves unpredictably once mapped into the guest's virtual root (silently landing elsewhere, failing withEPERMwhen traversed, or not being detected as a loop).