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
runtime: test output is very noisy #38594
Comments
An example (https://build.golang.org/log/dd547a9133c41d38ea6c4c0e5a7c5d8541c7b7b2):
I can't tell from that output what, if anything, all of those lines have to do with the failing |
That's in one of my tests, I clean that up. Thanks for pointing that out. |
Change https://golang.org/cl/229538 mentions this issue: |
…ess chatty Converted some Println() statements (used to make sure that certain variables were kept alive and not optimized out) to assignments into global variables, so the tests don't produce extraneous output when there is a failure. Fixes golang#38594 Change-Id: I7eb41bb02b2b1e78afd7849676b5c85bc11c759c Reviewed-on: https://go-review.googlesource.com/c/go/+/229538 Run-TryBot: Dan Scales <danscales@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
At some point recently (within the 1.15 cycle), the
runtime
test failures have started to include a lot of mysteriousrecurseFn
,methodN
anddid recover
noise that isn't clearly associated with any test function.Either the purpose of this output should be made clearer, or the output should be suppressed or clearly associated with a specific test.
Tentatively marking as release-blocker for 1.15, because if the
runtime
test fails on a user's machine I think this noise will make it very difficult for them to figure out what is wrong.CC @aclements @randall77 @danscales
The text was updated successfully, but these errors were encountered: