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/coverage: TestIssue59563TruncatedCoverPkgAll failures #59867
Comments
Found new dashboard test flakes for:
2023-04-27 14:07 linux-amd64-longtest go@e8c8b79f runtime/coverage.TestIssue59563TruncatedCoverPkgAll (log)
|
(attn @thanm) |
This looks like an issue with the test, I'll send a CL. |
Found new dashboard test flakes for:
2023-05-02 15:36 darwin-amd64-longtest go@2d83b646 runtime/coverage.TestIssue59563TruncatedCoverPkgAll (log)
|
Change https://go.dev/cl/492175 mentions this issue: |
Fix up the coverage testpoint TestIssue59563TruncatedCoverPkgAll to avoid spurious failures due to racy behavior. Specifically, we are only interested in verifying coverage for the larger function of the two in the test package (the smaller one is only there to trigger additional function registrations while the test is finalizing the cov data). Updates #59867. Updates #59563. Change-Id: Ibfbbcbf68e0ad7a4d9606cbcfc69d140375c7b87 Reviewed-on: https://go-review.googlesource.com/c/go/+/492175 Run-TryBot: Than McIntosh <thanm@google.com> Auto-Submit: Than McIntosh <thanm@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com>
This is in theory fixed with https://go.dev/cl/492175 ; leaving open for a while just in case there are still lingering problems. |
@thanm, it's been quite a while with no new |
Indeed, thanks. Closing out. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: