Uh oh!
There was an error while loading. Please reload this page.
test: remove deprecated error logging - #3079
Conversation
Trott
commented
Sep 27, 2015
evanlucas
commented
Sep 28, 2015
Don't we try to not use logging in tests at all? So should we just remove these statements totally vs replacing? |
Trott
commented
Sep 28, 2015
@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. |
Trott
commented
Oct 6, 2015
Bump: This looks good or the statements should just be removed altogether? |
evanlucas
commented
Oct 6, 2015
I would vote for just removing them. Not sure if other agree though |
Trott
commented
Oct 6, 2015
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.
bnoordhuis
commented
Oct 6, 2015
LGTM |
Trott
commented
Oct 7, 2015
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>
Trott
commented
Oct 7, 2015
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().