Merge List:
+ 2025-12-05 745349712e runtime: don't count nGsyscallNoP for extra Ms in C
+ 2025-12-05 f3d572d96a cmd/go: fix race applying fixes in fix and vet -fix modes
+ 2025-12-05 76345533f7 runt…
(1 comment)
Hmm, the https://go.dev/doc/telemetry page consistently uses "Go telemetry", and including toolchain might be misleading since "Go telemetry is only intended for use in programs maintain…
Thanks for reporting. That little triangle inside the "Latest" badge does say that the package doesn't exist in the latest version of the standard library, but admittedly it is small and pretty uncom…
Pull in the following x/tools changes:
- CL 726000: go/analysis/passes/modernize: omitzero: suppress on kubebuilder
- CL 726621: internal/refactor/inline: built-ins may affect inference
- CL 727041:…
Yes, the `wait-release` is used to indicate that CL can be submitted for the next Go release, because we've now entered a release freeze for Go 1.26. See https://groups.google.com/g/golang-dev/c/Om8V…
That CL finished propagating by now and so the 1.26 LUCI trybots should work. It looks like this CL just needed some change (such as your reply) to trigger them.
@adonovan@google.com Legacy trybots don't contain any builders by default anymore.
Normal LUCI trybot will start working soon for internal-branch.go1.26, see CL 726860.
Hi Kiran,
Thank you for your contributions, including helping maintain the s390x architecture, and for requesting trybot access. I've added you to the `may-start-trybots` group, so you should be abl…
Hi Kiran,
Thank you for your contributions, including helping maintain the s390x architecture, and for requesting trybot access. I've added you to the `may-start-trybots` group, so you should be abl…
Added this to Test Flakes project, otherwise watchflakes won't post to it.
Note that some of the matching failures in #68788 were on netbsd/arm64 and freebsd/riscv64, too. Perhaps they can be merged…
Thanks.
Maybe include a leading slash here, so it's clear that's the absolute path of that endpoint. Including the leading slash seems to be the pattern followed at https://go.dev/pkg/net/http/pprof…
Thanks for clarifying. Given the remaining fix might be complex, do you think it's worth trying to get it into Go 1.26, while we're still fairly early in the freeze? I applied the release-blocker lab…
@adonovan Checking in on the status here as this is a Go 1.26 RC 1 blocker. Or perhaps if what is left here is safe for after RC 1, then it can have okay-after-rc1 label added. Thanks.
@markus-kusano Checking in on the status here as this is currently marked as a Go 1.26 RC 1 blocker. Or perhaps this is safe after RC 1 and can have okay-after-rc1 label added. Thanks.
@mknyszek Checking in on the status here as this is a Go 1.26 RC 1 blocker. Or perhaps this is safe after RC 1 and can have okay-after-rc1 label added.
Thanks for working on this release note change.
At this time the release note fragments need to be assembled and moved to x/website, as part of preparing for Go 1.26 RC 1. Unfortunately that means y…
This change doesn't seem to be working towards increasing stability of Go 1.26 or resolving its release blockers, so it's probably okay to leave for Go 1.27.
Thanks.
The release note fragments need to be assembled and moved to x/website soon. If there's more follow up here, please aim to do in the soon to be merged [x/website/_content/doc/go1.26.md](http…
This was previously reported in issue #664. PR https://github.com/actions/setup-go/pull/667 was created to resolve this for v4.
It is already resolved in v6 as of [v6.1.0](https://github.com/actions…
Thanks for preparing this CL. I haven't looked closely at the new package yet, just leaving an initial comment in go.mod.
We need to keep x/build's go directive at 1.24 for a few months longer, whil…
We are indeed past the code freeze for Go 1.26, so enhancements and optimization CLs that haven't already been submitted do need to wait for the tree to reopen for Go 1.27 (expected in [late January]…
The linux-amd64-race race builder failed due to a timeout while testing the runtime package on first try. It doesn't seem to be related to this change and it passed on second try, so bypassing.
Constructing HostnameError.Error() takes O(N^2) runtime due to using a
string concatenation in a loop. Additionally, there is no limit on how
many names are included in the error message. As a result…
Constructing HostnameError.Error() takes O(N^2) runtime due to using a
string concatenation in a loop. Additionally, there is no limit on how
many names are included in the error message. As a result…
Constructing HostnameError.Error() takes O(N^2) runtime due to using a
string concatenation in a loop. Additionally, there is no limit on how
many names are included in the error message. As a result…
The official Go downloads page (https://go.dev/dl/) contains the most up-to-date URLs for individual Go release files. They follow the pattern `https://go.dev/dl/{file name}`, so for example the go1.…
The official Go downloads page (https://go.dev/dl/) contains the most up-to-date URLs for individual Go release files. They follow the pattern `https://go.dev/dl/{file name}`, so for example the go1.…
This is resolved in actions/setup-go by now, see https://github.com/actions/setup-go/releases/tag/v6.1.0. Copying what I posted at https://github.com/actions/setup-go/issues/664#issuecomment-34166816…
It sounds like this is resolved, but for future issue reports, please include answers to questions in the template. For questions, there's a list of better suited forums linked at [go.dev/wiki/Questi…
@qmuntal The commit message of [CL 724640](https://go.dev/cl/724640) contained "This avoids potential deadlocks during os package initialization" and "Updates #76391", so this issue is still open. Is…
This change happened upstream, and this is now done for cmd/pprof via [CL 725500](https://go.dev/cl/725500). (CC @prattmic.) Added this issue to the Go1.26 milestone.
Pull in the latest published version of github.com/google/pprof
as part of the continuous process of keeping Go's dependencies
up to date.
For #36905.
[git-generate]
cd src/cmd
go get github.com/go…
The Go 1.26 code freeze has recently started. This is a time to update
all golang.org/x/... module versions that contribute packages to the
std and cmd modules in the standard library to latest maste…
Thanks.
I'll also update other x repo packages for #36905 soon.
It's also in line with "The release freeze applies to the entire main repository as well as to the code in subrepositories that is ne…
@vasi Does this problem apply to Go 1.24 too? If so, we'll need to consider them both per [Go release policy](https://go.dev/issue/34536#issuecomment-572188389).
When watchflakes encounters a new failure mode that none of the existing issues in the Test Flakes project match, it creates a new issue for it. When it creates the issue, it creates a pattern for th…
Widened the pattern here to catch all Test/*.txt failures, otherwise watchflakes defaults to creating too many individual ones. (If their failure modes end up being different, they can be split up as…
```
#!watchflakes
default <- pkg == "cmd/go/internal/modfetch/codehost" && test ~ `^TestReadZip`
```
An issue for watchflakes to track flaky failures of this test.
CC @golang/command-line.
The Go porting policy has a section on broken ports, https://go.dev/wiki/PortingPolicy#broken-ports. The GOOS=freebsd GOARCH=riscv64 port was marked broken in August 2025 ([CL 691835](https://go.dev/…
@mengzhuo Thanks for working on this. The freebsd/riscv64 builder has passing runs on [some golang.org/x repos](https://ci.chromium.org/ui/p/golang/g/port-freebsd-riscv64/builders), but the main Go r…