Repository navigation
Module loader: a failed load of a replaced module must not leave its error on the replacement (tests for oven-sh/WebKit#754) #39711
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
robobun
wants to merge
1
commit into
main
Choose a base branch
from
farm/4ad8a864/module-loader-removed-entry-error
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Maintainers get six tests that fail in CI on every run after merging, if this lands before the engine fix it depends on is pinned. The commit message says the new tests "fail on main" and only pass with oven-sh/WebKit#754, but scripts/build/deps/webkit.ts:6 still pins WEBKIT_VERSION to fb1167ebf2cb9edc1f6771a2c11771b024693ae0 and nothing gates the tests. In a debug build the mock.module() case also stops at an assertion in fetchComplete(). Fix: land this only after WEBKIT_VERSION is bumped to a main SHA containing #754, or until then mark the six tests with test.todo/test.todoIf so a red run means a regression. Sites: test/js/bun/test/mock/mock-module.test.ts:544,585; test/js/bun/plugin/plugins.test.ts:1117,1165; test/cli/hot/hot.test.ts:832. [also at: test/cli/hot/hot.test.ts:833 - CI turns red for everyone after merging: six new tests fail against the WebKit this tree pins. The commit itself says they "fail on main" and pass only with oven-sh/WebKit#754, but scripts/build/deps/webkit.ts:6 still pins fb1167ebf2cb9edc1f6771a2c11771b024693ae0, which is the…; scripts/build/deps/webkit.ts:6 - Six new tests fail on the pinned engine, so merging turns CI red where the base is green. The pin at scripts/build/deps/webkit.ts:6 is
fb1167ebf2cb9edc1f6771a2c11771b024693ae0, main's tip from #44281, which holds oven-sh/WebKit#748 and #749 but not the loader fix of oven-sh/WebKit#754 that the HEAD commit says these tests need.]Why this was flagged
The trigger is merging this change while the pinned JavaScriptCore does not contain the fix in oven-sh/WebKit#754; the author's own commit message for 42c2823 says the six tests fail on main and pass only with that engine change. The change adds plain it()/test.concurrent() tests at test/js/bun/test/mock/mock-module.test.ts:544 and :585, test/js/bun/plugin/plugins.test.ts:1117 and :1165, and test/cli/hot/hot.test.ts:832, with no todo/skip gating. scripts/build/deps/webkit.ts:6 is unchanged by this commit and pins WEBKIT_VERSION = "fb1167ebf2cb9edc1f6771a2c11771b024693ae0", a main SHA from #44281, not a build of #754. On the base branch these tests do not exist, so the suite is green; after merging, every CI run on every PR reports these tests red, and on debug builds the mock.module() case hits the fetchComplete() assertion the message describes. No safeguard applies: the test runner has no engine-version gate and the tests do not check for the engine fix.
Verification: Commit 42c2823 does not touch scripts/build/deps/webkit.ts, whose line 6 still pins WEBKIT_VERSION fb1167ebf2cb9edc1f6771a2c11771b024693ae0. The six added tests at test/js/bun/test/mock/mock-module.test.ts:544 and :589, test/js/bun/plugin/plugins.test.ts:1117 and :1165, and test/cli/hot/hot.test.ts:832 have no .todo, .skip or version check. The pin's commit 7fe13e1 brings in only oven-sh/WebKit#748 and #749, not #754.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct, and that is why this PR is a draft. It must not merge before
WEBKIT_VERSIONis a main sha that contains oven-sh/WebKit#754. The pin moves in this PR once that engine change is merged, and the PR leaves draft then. I did not mark the tests as todo: they would then merge ahead of the fix, and a todo test does not fail when the bug comes back. This thread stays open until the pin is in.