-
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
test: remove deprecated error logging #3079
Conversation
Don't we try to not use logging in tests at all? So should we just remove these statements totally vs replacing? |
@evanlucas I know there are some folks who definitely think the tests should not have any I thought about just removing them, but I was afraid it would be a slippery slope. If I remove all these statements, why not remove all the console.error() statements in every test? But then we're talking about a very large set of changes, and I definitely favor narrower change sets. |
Bump: This looks good or the statements should just be removed altogether? |
I would vote for just removing them. Not sure if other agree though |
I started removing the calls to see if there were any issues. It helped find some dead code, actually. Sold. I removed them all and a few other nearby console logging calls. How's it look? |
common.error() is just deprecated util.error() renamed. Remove calls to it and some other extraneous console logging in tests.
LGTM |
One last CI for good measure before landing: https://ci.nodejs.org/job/node-test-pull-request/444/ |
common.error() is just deprecated util.error() renamed. Remove calls to it and some other extraneous console logging in tests. PR-URL: #3079 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Landed in 099cfbc. |
common.error() is just deprecated util.error() renamed. Remove calls to it and some other extraneous console logging in tests. PR-URL: #3079 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
common.error()
is justutil.error()
which is deprecated. Update instances toconsole.error()
.