Skip to content

Make sure that error() always generates failure in compiler.js #19184

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

Merged
merged 1 commit into from
Apr 17, 2023

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Apr 15, 2023

Previously we would report the error but then exit with 0.

@sbc100 sbc100 requested a review from kripken April 15, 2023 00:14
@sbc100
Copy link
Collaborator Author

sbc100 commented Apr 15, 2023

Split out from #18905

Previously we would report the error but then exit with 0 in some
cases.  For example in `--symbols-only` mode of if the error happened
after the first check of `abortExecution` in this file.

Also, change to use `Unknown preprocessor directive` other it will
be reported as "Internal compiler error", which it is not.
@sbc100 sbc100 changed the title Don't ignore errors in compiler.js --symbols-only Make sure that error() always generates failure in compiler.js Apr 17, 2023
@sbc100 sbc100 merged commit 5f84e88 into main Apr 17, 2023
@sbc100 sbc100 deleted the jsifier_error branch April 17, 2023 21:12
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