-
Notifications
You must be signed in to change notification settings - Fork 30k
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
src: add error codes to errors thrown in node_i18n.cc #28221
src: add error codes to errors thrown in node_i18n.cc #28221
Conversation
e375489
to
2528956
Compare
3d7fec8
to
400486b
Compare
400486b
to
3ec5081
Compare
I just started a "resume build" which will re-run just Windows at the same commit/rebase it did 4 days ago. That failure (test-statwatcher) was a very problematic unreliable issue that has since been fixed. If it fails again on the resume-build, we may just want to do a full re-run so that we rebase and get the fix. The problem with doing that right now is that we're having AIX problems in CI and AIX will undoubtedly fail for unrelated reasons. I would expect that AIX issue to get fixed in a few hours (once it's not the middle of the night for the relevant folks with expertise). This is probably too much detail, but the upshot is: If the re-run doesn't pass, feel free to ping again, don't hesitate. I've added an |
Landed in e6edd66 |
PR-URL: nodejs#28221 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
PR-URL: #28221 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
This PR follows #20121 and adds error codes to errors thrown in
node_i18n.cc
.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes