| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Oops, still need to fix these!
Sorry, something went wrong.
|
Here's the actual function in test/common.js: https://github.com/nodejs/node/pull/6697/files#diff-8736c5cbff21e1dee18b0c86d3d2689dR468 |
Sorry, something went wrong.
Sorry, something went wrong.
|
LGTM if CI has no complaints |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Nit: It might be good to name the function more precisely, as it does not actually skip. It outputs the TAP-formatted skip message. I would expect skip() to exit the process too. So either add process.exit() to skip() or else change the function to something like printSkipTapOutput() (although that's not exactly aesthetically pleasing). Totally a nit, feel free to ignore, I know process.exit() causes some trepidation in some situations, and I'm fine with this as it is. |
Sorry, something went wrong.
|
Maybe just printSkip(msg)? Idk |
Sorry, something went wrong.
|
The reason I went with this is iirc because it causes a skip even if the test fails afterwards? |
Sorry, something went wrong.
|
The more I think about it, I wouldn't expect a common.whatever() call to exit my process anyway, so it's probably a bad suggestion. |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
The tap skipping output is so prevalent yet obscure in nature that we ought to move it into it's own function in test/common.js PR-URL: nodejs#6697 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
The tap skipping output is so prevalent yet obscure in nature that we ought to move it into it's own function in test/common.js PR-URL: #6697 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
|
@Fishrock123 I'm going to put this in dont-land-in-lts but please feel free to do a manual backport |
Sorry, something went wrong.
|
Huh. Backporting doesn't seem to work at all. 10 obscure errors. I'll just redo the patch for v4.x, it shoudn't be difficult, and this will likely cause backport conflicts if we don't. |
Sorry, something went wrong.
|
@Fishrock123 that's what I figured would happen. Totally up for the manual backport thanks 👍 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
test
Description of change
The tap skipping output is so prevalent yet obscure in nature that we ought to move it into it's own function in test/common.js
cc @nodejs/testing