Skip to content
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

Revert "Continue work on new module registry" #3401

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

mikea
Copy link
Collaborator

@mikea mikea commented Jan 23, 2025

Breaks things downstream, not sure why.

Reverts #3372

@mikea mikea requested review from a team as code owners January 23, 2025 18:35
@mikea mikea requested review from npaun and jp4a50 January 23, 2025 18:35
@jasnell
Copy link
Member

jasnell commented Jan 23, 2025

Specifically, breaks internal fuzzing tests. Will investigate in the next day or two then try again.

@mikea mikea merged commit 148f755 into main Jan 23, 2025
17 checks passed
@mikea mikea deleted the revert-3372-jasnell/continue-on-new-module-registry branch January 23, 2025 18:55
@jasnell
Copy link
Member

jasnell commented Jan 23, 2025

Investigation is actually pointing to the internal fuzzer-asan issue is likely a false positive. The same error occurs with or without this change in various tests. It would suggest that the internal bazel build configuration is not being appropriately applied to workerd when testing such that parts of the code are instrumented and other parts are not. Still digging but that's the current hypothesis. I believe this PR just surfaced the issue in testing but did not actually introduce any actual bugs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants