Bump component-test to eabd159; slim the jco legs onto the upstream loop - #38
Merged
Conversation
The pin moves via pins bump. harness.mjs's runSuite becomes a thin adapter over the upstream runSuiteJsonl (polymorph-test#70) — the case loop, fresh-instance policy, envelope, and terminator live upstream; the local wrapper keeps this repo's newInstance/coreBytes signature for both legs, and stays browser-loadable (the page runs it unchanged, which also exercises the upstream loop in Chromium). run-node.mjs drops its local core loading and results-file writing for the ./node-runner helpers. Verified: conformance-ct::all green including the browser leg (4 targets, 220 results, matrix unchanged), check-js, wpt::parity.
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.
Routine pin bump (via
pins bump) carrying polymorph-test#70.harness.mjs'srunSuitedelegates to the upstreamrunSuiteJsonl(keeping its local signature for both legs — and since the browser page loads this module unchanged, the upstream loop gets exercised in Chromium here);run-node.mjsswaps its local core-loading and results-writing for./node-runner. The tests-export access stays inline (.tests) rather than usingresolveTestsExport, which currently lives in the node-only module while this file is browser-shared — relocating it browser-safe rides the #59 browser-driver PR. Verified:conformance-ct::allgreen with the browser leg (4 targets, 220 results, matrix unchanged),check-js,wpt::parity.