-
Notifications
You must be signed in to change notification settings - Fork 17.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
x/telemetry/internal/regtest: test consistently failing on many platforms since CL 560462 #65544
Comments
It is also worth noting that this test does not meet the standard of https://go.dev/wiki/CodeReviewComments#useful-test-failures: it shows what was got and what was expected, but it does not describe “with what inputs” and doesn't report any errors encountered by the telemetry collection & upload process. |
I believe @pjweinb has a fix for this in https://go.dev/cl/561995. |
Nevermind, that CL removes the proxy API which I still believe is necessary. I'll send a fix for the builder breakage. |
Change https://go.dev/cl/562076 mentions this issue: |
Change https://go.dev/cl/562396 mentions this issue: |
Change https://go.dev/cl/563359 mentions this issue: |
For golang/go#65544 For golang/go#65549 Change-Id: Icb8d598e419e6b34c184642a851a699be8b76382 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/563359 LUCI-TryBot-Result: Go LUCI <[email protected]> Auto-Submit: Hyang-Ah Hana Kim <[email protected]> Reviewed-by: Robert Findley <[email protected]>
Go version
9819d82
Output of
go env
in your module/workspace:What did you do?
Check builder status for #11811.
What did you see happen?
https://build.golang.org/log/3ea3d15a5b41086aeb875a6846533cb78175b83b:
This affects all
386
platforms, including the first class ports forlinux/386
andwindows/386
.Similar failures occur on the
android
,illumos
,js
,openbsd
,plan9
,solaris
, andwasip1
builders, although since those are secondary ports perhaps they are just misconfigured builders.What did you expect to see?
All tests should be either passing or skipped, especially on first class ports such as
linux/386
andwindows/386
.For secondary ports that are intentionally not supported, either the tests should be skipped or the builders should be configured not to run them in the first place.
The text was updated successfully, but these errors were encountered: