(2 comments)
Done in PS 2.
I filed a separate issue to clean up the unused App Engine app.
Done.
I mentioned them both since right now https://perf.golang.org/ has no link or any indication that …
(1 comment)
Thanks for correcting this. For some reason I was under the impression the ingress at https://cs.opensource.google/go/x/build/+/master:deploy/build-ingress.yaml;l=116;drc=7bf60f09df7b988…
Issue #78074 is due to [CL 751260](https://go.dev/cl/751260) adding an unconditional write to `ml.data[2]`, and the `ml.data` slice being given a size of `len(load.cmd.data)` which has few than 3 ele…
(1 comment)
It's probably fine that p.To.Name is set to obj.NAME_NONE here and seemingly not changed to another value later, but calling it out just in case.
Thanks.
https://ci.chromium.org/ui/p/golang/builders?q=-darwin-arm64_26 is all green except go1.25-darwin-arm64_26, but that one should be fixed by the stack ending with CL 753681.
The new dynamic loader in macOS 26 beta doesn't like binaries
without LC_UUID. Binaries built by "go build" have LC_UUID by
default. When invoking the linker manually, it has an LC_UUID by
default if…
Thanks. Those CLs only modify a package that contains tests, and isn't used otherwise, so they should be safe. It's all that's left to get Go 1.25's all.bash passing on macOS 26, so I suggest we back…
[CL 751465](https://go.dev/cl/751465) fixed #77781 but caused linux/arm to run into a https://ci.chromium.org/b/8687988093932136273 failure mode. As of [CL 752560](https://go.dev/cl/752560), the fail…
Thanks. Be mindful that I'm not very familiar with potential nuances here but the change seems reasonable.
In contrast to vcsRepo.Stat, where rev == "latest" is cached like any other revision, here …
Thanks.
(Asking to learn.) Is there some functionality that maps this .txt file's txtar content with .mod to a go.mod file? Yes, found it via [README](https://cs.opensource.google/go/go/+/master:src…
### Go version
```sh
# (on macOS 26)
$ go version
go version go1.25.8 darwin/arm64 # with go.dev/cl/752520 applied on top
```
### What did you do?
Ran `go test -count=1 cmd/cgo/internal/test`.
#…
The watchflakes pattern only matches the legacy builder, not the newer one that was moved to LUCI. If this happens on the new builder, watchflakes will open a new issue.
The watchflakes pattern only matches the legacy builder, not the newer one that was moved to LUCI. If this happens on the new builder, watchflakes will open a new issue.
The watchflakes pattern only matches the legacy builder, not the newer one that was moved to LUCI. If this happens on the new builder, watchflakes will open a new issue.
The relevant part of the test log is:
```
buildrelease_test.go:743: task illumos-amd64: Reproduce distpack on Windows: error: script failed: exit status 139 output:
+ set -o pipefail
…
Thanks. FWIW, I found this because the [gotip-darwin-amd64_15](https://ci.chromium.org/ui/p/golang/builders/ci/gotip-darwin-amd64_15) builder being added (issue #77997) ran into this 4 times in a row…
A test in C has an array bound defined as a "const int", which is
technically a variable. The new version of C compiler in Xcode 26
beta emits a warning "variable length array folded to constant
arra…
Thanks. Since this is a test-only fix, and should be safe, we can probably backport it. (Another option would be to skip the test, but that doesn't seem to be needed.)
@gopherbot Please consider thi…
The recently added darwin/arm64 builder with macOS 26 (issue #76798) uncovers a failing test on [release-branch.go1.25](https://ci.chromium.org/ui/p/golang/builders/ci/go1.25-darwin-arm64_26):
I can…
This is a tracking issue for adding darwin/amd64 builders with macOS 15 (macOS Sequoia).
We already have darwin/arm64 builders ones with it as of #73397.
CC @golang/release, @golang/darwin.
One of the things left out of initial scope of #77214 was:
> upstreaming to main branch - this has a lot in common to release branches, but we don't have an existing ref for this and there are more …
The CL still needs to complete the [code review process](https://go.dev/doc/contribute#reviews). It already has reviewers added to it, but perhaps they haven't found the time to get to it. Since it's…
Oh, I missed the earlier https://github.com/golang/go/issues/77945#issuecomment-3999348983 where it was mentioned. That looks like an improvement as far as I can tell, so if you don't mind please do …
Relui may need more scratch space to work with when running tasks
that involve cloning large repositories, such as when upstreaming
private-track security CLs on the release day.
The previous value …
The TestListenIPv6WildcardAddr test was recently added in [CL 743080](https://go.dev/cl/743080) (CC @ravisastryk, @nicholashusin), and it's consistently failing on openbsd/amd64 and openbsd/ppc64 por…
The builder has been added and it's passing all.bash in the main repo.
Move it from TBD_CAPACITY_HOSTS to LOW_CAPACITY_HOSTS and drop its
skip_x_repos option to get closer to fully removing its known…
[CL 664235](https://go.dev/cl/664235) updated this section. @matloob Was this issue perhaps intended to be closed by it? (Its commit message said "Fixes #57355" which seems to be 404, and this issue …
(1 comment)
Indeed. There's no merge conflict because both CLs made an identical change here, so once rebased, only the fix on line 279 will be applied. Rebasing would be required if there was a mer…
I suggest starting with a brief issue describing this change, and include `CC @golang/security` to let the [owners](https://dev.golang.org/owners) of these packages know. They'll have a better idea w…
Should a change like this also have tests, updated documentation, and a reference to an issue (or a proposal if this is considered notable enough)? Possibly also a release note for Go 1.27?
Without …
Make it easier to maintain (and unify) deployment files for x/build
services by having the commands uniformly live in the cmd directory.
For golang/go#70913.
(1 comment)
> Didn't know gopherbot will close issues for CLs landed on internal-vendor branch.
Ah, I was mistaken when I anticipated that happening, sorry for a misleading comment. It indeed won't…
@dagood The change in x/tools repo in [CL 747560](https://go.dev/cl/747560) hasn't been vendored into the main Go repo yet. That will certainly happen in time for Go 1.27 (this issue's milestone), tr…
(1 comment)
Note that this CL alone won't fix #77899; the CL that pulls this change into the [main Go repo's release branch](https://cs.opensource.google/go/go/+/release-branch.go1.26:src/cmd/go.mod…
As an alternative to running 'go build', 'go clean', then 'go install', would it work to skip the first two steps and run 'go install' right away? If there's a build error, 'go install' would report …
@dr2chase This backport issue is still open but without CherryPickApproved nor CherryPickCandidate label. Should this go back to approved but with [CL 749241](https://go.dev/cl/749241) as the new CL …
We reviewed and approved this during a release meeting, moved CherryPickApproved from https://github.com/golang/go/issues/77737#event-23078589596 to this issue. (CC @dr2chase.)
This issue was marked as fixed by [CL 747900](https://go.dev/cl/747900), but that CL is in the main branch of x/tools. That's sufficient to fix the problem in time for Go 1.27, but this issue is curr…
We reviewed and approved this during a release meeting, moved CherryPickApproved from https://github.com/golang/go/issues/77659#event-23078585370 to this issue.
We reviewed and approved this during a release meeting, moved CherryPickApproved from https://github.com/golang/go/issues/77482#event-23078592981 to this issue.
They are. Although Go can make them too easy via `go:embed`.
See some initial comments.
I suggest either adding a quite that can be licensed via the existing BSD-3-Clause LICENSE at the top level o…