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: TestMemPprof failures #60901
Comments
Found new dashboard test flakes for:
2023-06-20 18:25 linux-amd64-longtest go@8484f2fe runtime.TestMemPprof (log)
|
See also #57149. |
This is notably in the |
In triage, it's very weird that we got a |
@prattmic suggests that maybe we jumped to the wrong address, because we pad functions with |
To get more information, Cherry is going to change the test runner in this case to actually dump whatever the subprocess that failed here wrote to stdout/stderr. Right now we have very little to go on. |
Change https://go.dev/cl/507978 mentions this issue: |
If running testprog fails, print the output. For #60901. Change-Id: Iee80fb09412ce13bae6ac3589779a8cdf7761765 Reviewed-on: https://go-review.googlesource.com/c/go/+/507978 Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com>
If running testprog fails, print the output. For golang#60901. Change-Id: Iee80fb09412ce13bae6ac3589779a8cdf7761765 Reviewed-on: https://go-review.googlesource.com/c/go/+/507978 Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com>
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: