-
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
deps: revert default gtest reporter change #8948
Conversation
I made that change intentionally. Why would you want a different output format locally? |
Can we leave the tap output for |
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. |
If you want CI output, just run |
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. |
It's harder to read and also inconsistent. |
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. |
I'm not ok with that as it would mean scrolling through a few thousand lines of terminal text to find an error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
If you really want it, we can make |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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 |
@jasnell Are you saying |
@mscdex... For now, |
03824c8
to
a205a9e
Compare
Ok, I've added CI again: https://ci.nodejs.org/job/node-test-pull-request/4410/ |
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 |
@@ -169,6 +169,9 @@ static const char kUniversalFilter[] = "*"; | |||
// The default output file for XML output. | |||
static const char kDefaultOutputFile[] = "test_detail.xml"; | |||
|
|||
// The default result reporter format. | |||
static const char kDefaultResultFormat[] = "pretty"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unused.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
@@ -438,6 +446,17 @@ std::string UnitTestOptions::GetAbsolutePathToOutputFile() { | |||
return result.string(); | |||
} | |||
|
|||
// Functions for processing the gtest_result_format flag. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this supposed to be singular, Function
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with the nits raised by @thefourtheye addressed.
a205a9e
to
f9ad5da
Compare
@bnoordhuis Is this acceptable to you ( |
If the choice is between no TAP output locally or carrying more patches on top of gtest, I'd rather go with the former. |
f9ad5da
to
cebefd4
Compare
@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. |
@bnoordhuis no, let me fix that now. Just very tedious working with jenkins jobs when its slow :'( |
@bnoordhuis just did a test run with aix61. Looks good -- do you agree? https://ci.nodejs.org/job/node-test-commit-aix/1508/ |
@jbergstroem Yes, looks good, thanks. |
@bnoordhuis cool. Will roll out the change now. |
c133999
to
83c7a88
Compare
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. |
d12ed28
to
cd3b53e
Compare
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>
cd3b53e
to
6e5389e
Compare
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>
Checklist
make -j8 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected 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/