-
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/mobile/cmd/gobind: TestGobind/.*/Go-Cgopkg broken at CL 437298 #56292
Comments
(I do see an |
My previous change might cause this issue. I'll take a look |
Change https://go.dev/cl/443655 mentions this issue: |
I cleaned up the test output in https://go.dev/cl/443655, and got the error output down to something more comprehensible:
|
Hm, I couldn't reproduce the issue on my local machine...
|
(CC @matloob) |
Change https://go.dev/cl/443656 mentions this issue: |
…ault Using the test binary as the "gobind" command not only avoids the overhead of recompiling the command, but also allows commands like "go test -race" to actually test the requested configuration of the command. Logging stderr and stdout separately — and logging only stderr by default — makes the failure messages much easier to spot. (Logging the combined output as before produced a massive wall of text that tends to bury the actual errors.) For golang/go#56292. Change-Id: Ia11fad19418d9b9004608c76fe512ceab4f247bc Reviewed-on: https://go-review.googlesource.com/c/mobile/+/443655 Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Hajime Hoshi <hajimehoshi@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: David Chase <drchase@google.com>
Also update to "go 1.17" to enable module graph pruning. For golang/go#56292. Change-Id: I1d1f4a2625d36d4c8587080e391d3e2c2e7f7808 Reviewed-on: https://go-review.googlesource.com/c/mobile/+/443656 Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Hajime Hoshi <hajimehoshi@gmail.com> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: David Chase <drchase@google.com>
@hajimehoshi This is reproducible only with the go built on tip in the path (after cl/437298)
With cl/437298 (that is a bug fix IMO), the error is reported in the Error field and eventually in go/packages.Package's Errors.
As a result, the Before cl/437298,
This failure error is reported as a But it looks like
There are some heuristic scanning of The previous bug depended on the bug in |
Change https://go.dev/cl/443935 mentions this issue: |
Gobind utilizes golang.org/x/tools/go/packages.Load to find the directory of a package. Configure the load configuration to just find the list of files. Zero load mode is equivalent to combining NeedName+NeedFiles+NeedCompiledGoFiles bits. That is unnecessary, and can increase the chance of load failures. For example, load with the zero load mode may fail if all the necessary cgo dependencies aren't available in the system, but that shouldn't be critical for gobind's use case. Updates golang/go#56292 Change-Id: Ifaf4f43e9053cf4a43fd657a9a394fc13f611576 Reviewed-on: https://go-review.googlesource.com/c/mobile/+/443935 Reviewed-by: David Chase <drchase@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Hajime Hoshi <hajimehoshi@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
Verified long builder passed with this commit. |
https://build.golang.org/log/c656c3d100391699f5e7a0389263d3a2be0a6497:
The first failure on the dashboard was at https://go.dev/cl/437298, although the
x
repos don't always test every Go commit.Unfortunately, since these tests don't produce useful failure messages, it's hard for me to tell why they're even failing.
(attn @hyangah per https://dev.golang.org/owners; CC @hajimehoshi @golang/android @golang/ios)
The text was updated successfully, but these errors were encountered: