-
Notifications
You must be signed in to change notification settings - Fork 30k
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: add PASS to outcomes in debug mode #25698
Conversation
I'll take a look at the code to see if it makes sense to make this change in code and not in configuration... |
Thank you, I just stumbled over this myself :) |
Currently, when configuring with --debug there is a lot of output from tests that use console.log. I believe that this was not the case prior to commit deaddd2 ("tools,test: add list of slow tests"). The motivation for this commit is that I find it difficult to distinguish real errors from tests that log errors when running in debug mode. This commit updates test/root.status to also include a PASS status so that this output is not displayed. If a tests fails then running the test directly will show the output.
@refack Did you get a chance to look at a code change for this? If not, could we land this and perhaps you could follow up separate PR? |
@richardlau Thanks, closing this favour of #25868 |
H/T to @hashseed to following up (while reading my mind) |
Ran into this while testing my gn build :D |
Currently, when configuring with
--debug
there is a lot of output fromtests that use console.log. I believe that this was not the case prior
to commit deaddd2 ("tools,test: add list of slow tests").
The motivation for this commit is that I find it difficult to
distinguish real errors from tests that log errors when running in debug
mode. This commit updates test/root.status to also include a PASS status
so that this output is not displayed. If a tests fails then running the
test directly will show the output.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes