-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
cmd/go: multi-arch build via qemu fails to exec go binary [1.23 backport] #68995
Labels
CherryPickApproved
Used during the release process for point releases
compiler/runtime
Issues related to the Go compiler and/or runtime.
GoCommand
cmd/go
telemetry
x/telemetry issues
Milestone
Comments
gopherbot
added
the
CherryPickCandidate
Used during the release process for point releases
label
Aug 21, 2024
gopherbot
added
the
compiler/runtime
Issues related to the Go compiler and/or runtime.
label
Aug 21, 2024
Change https://go.dev/cl/609136 mentions this issue: |
prattmic
changed the title
syscall: multi-arch build via qemu fails to exec go binary [1.23 backport]
cmd/gp: multi-arch build via qemu fails to exec go binary [1.23 backport]
Aug 28, 2024
prattmic
changed the title
cmd/gp: multi-arch build via qemu fails to exec go binary [1.23 backport]
cmd/go: multi-arch build via qemu fails to exec go binary [1.23 backport]
Aug 28, 2024
prattmic
added
CherryPickApproved
Used during the release process for point releases
and removed
CherryPickCandidate
Used during the release process for point releases
labels
Aug 28, 2024
gopherbot
pushed a commit
to golang/telemetry
that referenced
this issue
Aug 28, 2024
…ld could not be started Instead of calling log.Fatal if the child could not be started, call log.Print. Various factors in the user's environment could cause the child to not be able to start, but that shouldn't crash the parent process (usually the go command). Change other fatals into prints with early returns when attempting to start the child. Reset the crash output file to clean up if the child process could not be started and crashmonitoring is enabled. Updates golang/go#68976 Updates golang/go#68995 Change-Id: I42f55dc90f68f91b272a7ebf64d2a4a3b00815c7 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/607595 Commit-Queue: Michael Matloob <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Robert Findley <[email protected]> (cherry picked from commit 61baa7d) Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/609136
Change https://go.dev/cl/609355 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Aug 29, 2024
…ranch.go1.23-vendor Update x/telemetry to fix #68976 and #68946. Commands run: go get golang.org/x/[email protected] go mod tidy go mod vendor Fixes #68994. Fixes #68995. Change-Id: I63b892ad4c313aa92f21fbd4f519a0b19d725849 Reviewed-on: https://go-review.googlesource.com/c/go/+/609355 LUCI-TryBot-Result: Go LUCI <[email protected]> Auto-Submit: Michael Pratt <[email protected]> Reviewed-by: Robert Findley <[email protected]>
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CherryPickApproved
Used during the release process for point releases
compiler/runtime
Issues related to the Go compiler and/or runtime.
GoCommand
cmd/go
telemetry
x/telemetry issues
@findleyr requested issue #68976 to be considered for backport to the next 1.23 minor release.
The text was updated successfully, but these errors were encountered: