| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I made that change intentionally. Why would you want a different output format locally? |
Sorry, something went wrong.
|
Can we leave the tap output for make test-ci and use the pretty one locally? There's not really a reason to have tap output in the local tests. |
Sorry, something went wrong.
|
I think consistency with the CI is a pretty good reason. Libuv does the same thing; it makes visually comparing the output of local and remote runs a lot easier. |
Sorry, something went wrong.
|
If you want CI output, just run make test-ci -- we aren't the same as Libuv. Do you want to change the JS test output too? If not, this should be reverted for local tests. |
Sorry, something went wrong.
|
You asked for a reason and I gave you one. You are welcome to disagree but at least try to come up with a counterargument. |
Sorry, something went wrong.
|
It's harder to read and also inconsistent. |
Sorry, something went wrong.
|
Readability is subjective but I agree it's inconsistent. Then again, so is the normal gtest output vis-a-vis the JS test runner and the linters. It doesn't bother me personally but I'm okay with switching to TAP wholesale if you think consistency is important. |
Sorry, something went wrong.
|
I'm not ok with that as it would mean scrolling through a few thousand lines of terminal text to find an error. |
Sorry, something went wrong.
There was a problem hiding this comment.
I'll -1 as a counterweight to your +1 because I don't think your readability and consistency arguments are convincing. Besides, I like the new format.
Sorry, something went wrong.
|
If you really want it, we can make make test-tap. It is far easier to do that than update all the docs references to point to some new make test-pretty for everyone new coming here. |
Sorry, something went wrong.
There was a problem hiding this comment.
Yeah, I have to agree with @Fishrock123 and @mscdex here… being greeted by a tap Wall of Text doesn’t seem very helpful to me.
So, +1 to the revert here, although I realize that this is purely subjective from me, too.
Sorry, something went wrong.
|
fwiw, I'm partial to the new formatting but will go with whatever the majority opinion is here. Perhaps rather than simply revert, this PR could add a test-tap target for those of us who prefer it. |
Sorry, something went wrong.
|
@jasnell Are you saying test-tap would output TAP just for cctest but use progress indicators/"pretty print" for all other tests (like it is before this PR), or? |
Sorry, something went wrong.
|
@mscdex... For now, test-tap would use the current behavior (before this revert). Eventually I'd like to see test-tap do the full output as TAP. |
Sorry, something went wrong.
|
Ok, I've added test-tap that uses a new flag to configure the default printed result format. CI again: https://ci.nodejs.org/job/node-test-pull-request/4410/ |
Sorry, something went wrong.
|
It'd be really useful to have both TAP and pretty formats available for running tests, I frequently find myself using both. Is it possible to have the gtest pretty format match the tools/test.py pretty format? Ideally you'd just have the one line for everything (assuming no failures). |
Sorry, something went wrong.
There was a problem hiding this comment.
Unused.
Sorry, something went wrong.
There was a problem hiding this comment.
Updated.
Sorry, something went wrong.
There was a problem hiding this comment.
Isn't this supposed to be singular, Function?
Sorry, something went wrong.
There was a problem hiding this comment.
I kept it that way for consistency in case more are added in the future. I see it as more of a list heading than a comment for the one function.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM with the nits raised by @thefourtheye addressed.
Sorry, something went wrong.
|
@bnoordhuis Is this acceptable to you (make test-tap)? |
Sorry, something went wrong.
|
If the choice is between no TAP output locally or carrying more patches on top of gtest, I'd rather go with the former. |
Sorry, something went wrong.
|
@jbergstroem Did you ever make the change to make the CI pick up cctest.tap? Looking at e.g. https://ci.nodejs.org/job/node-test-commit-linux/5713/nodes=centos5-32/console I get the impression it doesn't currently. |
Sorry, something went wrong.
|
@bnoordhuis no, let me fix that now. Just very tedious working with jenkins jobs when its slow :'( |
Sorry, something went wrong.
|
@bnoordhuis just did a test run with aix61. Looks good -- do you agree? https://ci.nodejs.org/job/node-test-commit-aix/1508/ |
Sorry, something went wrong.
|
@bnoordhuis cool. Will roll out the change now. |
Sorry, something went wrong.
|
CI once more before landing: https://ci.nodejs.org/job/node-test-pull-request/4626/ EDIT: CI is green except for a few flaky tests on freebsd and pi1. |
Sorry, something went wrong.
PR-URL: nodejs#8948 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #8948 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #8948 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs#8948 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #8948 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
Description of change
The default gtest reporter changed in c56ae16 from a pretty printing reporter to TAP. This caused TAP output to be displayed when running make test locally (outside of CI). This commit reverts that particular change.
/cc @bnoordhuis @jasnell
CI: https://ci.nodejs.org/job/node-test-pull-request/4405/