-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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 arguments.callee usage #3167
Conversation
arguments.callee is forbidden in strict mode and the fact that it's being used masked a possible error in this test.
Change LGTM, I am okay if the CI is okay. |
CI: https://ci.nodejs.org/job/node-test-pull-request/412/ For the record, this change should've been done when we turned all tests into strict mode, pretty much an oversight on my part. |
@silverwind Mmmm yeah. But how it was not failing the builds till now? |
@thefourtheye because it only errors when it reaches a failure condition. If the test passes, the strict mode warning is never reached. What we have here, is a masked error on the linked test. |
FWIW: this is the only remaining use of |
LGTM, failures are unrelated. |
LGTM |
arguments.callee is forbidden in strict mode and the fact that it's being used masked a possible error in this test. PR-URL: #3167 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]>
Thanks, landed in 342c3a1. |
arguments.callee is forbidden in strict mode and the fact that it's being used masked a possible error in this test. PR-URL: #3167 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]>
arguments.callee
is forbidden in strict mode and the fact that it's being used masked a possible error in this test like in this case:https://ci.nodejs.org/job/node-test-binary-arm/101/RUN_SUBSET=0,nodes=pi1-raspbian-wheezy/tapTestReport/test.tap-39/