Open bcmills opened 9 months ago
Issue #17626 was having golang.org/x trybots have any kind of coverage for previous supported Go releases. The linux/amd64 builder was chosen as it was highly available and least expensive, and was a significant improvement compared to no coverage at all. But, it indeed is limited and doesn't catch problems that affect other OSes only on older Go versions.
It would certainly be good if we're able to expand this to cover more ports, and since we already consider breakages in first-class ports to block releases, adding first-class port trybot coverage makes a good next target. Adding FeatureRequest label since this is an enhancement.
Go version
a95136a88cb8a51ede3ec2cdca4cfa3962dcfacd
Output of
go env
in your module/workspace:What did you do?
Observe #65223.
What did you see happen?
Test failures for the
x/sys
repo onrelease-branch.go1.20
onwindows
as of https://go.dev/cl/556895, which had aLUCI-TryBot-Result +1
vote.What did you expect to see?
Since https://go.dev/cl/556895 had a passing TryBot run, it should not have introduced failures on any supported release branch on any first class port.