Expand static Test262 execution and exception behavior - #486
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ctate
force-pushed
the
ctate/test262-static-progress
branch
from
September 27, 2026 14:08
83e2132 to
94ca2d1
Compare
This branch was successfully 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
1 participant
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.
Static scriptc can now run more of the pinned Test262 suite through its adapted harness. The runner supports
assert.throws, asynchronous$DONEcompletion, and source-matched parse negatives while retaining explicit exclusions where the adapter cannot preserve Test262 semantics.The compiler and runtime changes preserve caught error object behavior and lower both handlers of
Promise.then. C and LLVM differential corpus cases cover these behaviors.Validation: focused Test262 regression profile, C and LLVM corpus checks, workspace build, compatibility checks, and
pnpm test:sandbox(plain and sanitized lanes) passed.