Activity

Today
This change is ready for review.
The previous link is shorter, but it's no longer indexed. Point to the new view to golangbuild source code where search indexing is available.
Yesterday
Thanks. I'll note that it's somewhat unclear how exactly values would be represented in some of the fields because they're not documented: for example, `Changelists []string` might be a slice of URL…
The release branch is currently frozen until the [Go 1.26.2 release](https://groups.google.com/g/golang-announce/c/2UyQAnUQKwc) is complete, added a temporary Hold+1.
This generally looks reasonable, thanks for working on it. Have you had a chance to try generating the gles bindings afterwards, and does the generated output seem okay? I think it'd be a matter o…
Thanks. Minor comments. Nit, https://go.dev/doc/contribute#first_line suggests leaving out the period; the period is a part of the "This change modifies Go to _____." sentence being completed. ```s…
This Week
Thanks. ```suggestion add support for non-standard chroma subsampling ratios" (CL 738280). ``` So that it's easier to get to if desired. Gerrit linkifies such CL mentions, and it's also possible to…
Last Week
dmitshur starred znkr.io/diff3d
It was another test failing, rangegen.go. It might've just been unlucky, it happens fairly often based on its history: https://ci.chromium.org/ui/test/golang/cmd%2Finternal%2Ftestdir%3A6_10.Test%2Fra…
Pull in https://github.com/fflewddur/ltbsky/pull/5.
Thanks for the report. CC @golang/tools-team.
(1 comment) This isn't right: the known issue should keep this an optional security trybot. Done in PS 2.
This consistent failure on ppc64 and loong64 is due to https://go-review.googlesource.com/c/go/+/750200/comments/58cbcdce_f20cfeba. CC @Jorropo, @golang/ppc64, @golang/loong64.
(1 comment) FWIW since its value is actually 20, I understand this means "just use its value by picking a value that's higher than maxHash by some reasonable margin so that it'll be some time before…
Thanks. Thanks for the clarification.
(1 comment) Did something go wrong with your "gofmt-on-save"?
(1 comment) Or, maybe the problem being fixed is that once someone with an old toolchain upgrades _to_ 1.25.x or 1.26.x (via go.dev/doc/toolchain), this change (once backported to 1.25.x and 1.26.x)…
(1 comment) A question about this; I'm not sure I understood this sequence properly. In the issue comment you described the problem as affecting Go 1.24 and older toolchains upgrading to Go 1.25+. B…
Do keep a known issue for Go 1.26 and 1.25 release branches since it doesn't work there yet (but may work soon). For golang/go#74985.
Thanks. I think this is right. You can give some more time for another review since Cherry is more familiar with this code, up to you.
net/smtp failures are likely #77504, so rebasing should resolve them.
@gopherbot Please consider backporting this issue (fixed by [CL 740480](https://go.dev/cl/740480) with a potential followup in [CL 747660](https://go.dev/cl/747660)). The linux/arm64 builder with Deb…
Thanks. Sounds good. (It's possible to follow up in the unlikely case it does need attention.) Thanks for taking release branch into consideration when removing the known issue.
The bfd linker has been fixed for a while. In the mean time gold got deprecated and has stopped receiving new features. Add runtime version checking and only use gold, if bfd ld 2.35 and lower is det…
That problem was tracked in #22040, and [CL 740480](https://go.dev/cl/740480) resolved it. The [linux-arm64_debian13](https://ci.chromium.org/ui/p/golang/builders/ci/gotip-linux-arm64_debian13) is no…
dmitshur commented on runtime/race: TestOutput failures4d
A race reported during this test's execution. The test has otherwise been passing without reported races. CC @golang/runtime.
dmitshur commented on internal/godebugs: TestAll failures4d
It looks like the internal/godebugs package tests often come quite close to the 6 minute timeout, e.g., past runs have taken 325.885s and similar. And in this case it went over the time limit, causin…
This looks similar to #55260, but in this case it is some telemetry files being left behind. So far only happened once on a linux-ppc64le builder. CC @golang/command-line.
There haven't been any matches since 2023, so perhaps this is fixed by various cmd/go test refactoring. There is a new instance in #78397 but it's related to telemetry files rather than vcstest files…
There haven't been any matches since 2023, so perhaps this is fixed by various cmd/go test refactoring. There is a new instance in #78397 but it's related to telemetry files rather than vcstest files…
dmitshur commented on syscall: TestPidFD failures4d
This test timed out running for 323 seconds. From looking at this [test history](https://ci.chromium.org/ui/test/golang/syscall.TestPidFD), it's almost always passing and usually takes something lik…
If this is a question, please see http://go.dev/wiki/Questions for places that are better suited for asking questions. The Go issue tracker is used for bugs, feature requests, optimization issues. D…
CC @golang/compiler.
CC @dsnet, @bradfitz.
CC @ianlancetaylor, @thanm, @cherrymui.
CC @golang/windows, @ianlancetaylor.
CC @golang/darwin, @bradfitz, @kevinburke.
This change is deployed now.
Something went wrong with the builder infrastructure in this instance. The x/vulndb tests passed, but the task log failed at the end with: ``` RPC failed permanently: rpc error: code = DeadlineExcee…
Release branches are used for backport CLs (https://go.dev/wiki/MinorReleases). Closing in favor of CL 751120, which is the same change that targets the main development branch.
It seems ready now, so dropping hold.
A builder is added and it's working. More instances may get added later. Fixes golang/go#77997.
The work needed to add darwin/amd64 builders with macOS 26 is somewhat different, so factored that out into its own tracking issue #78388. Retitled this to be about darwin/arm64 only, which is done. …
This is a tracking issue for darwin/amd64 builders with macOS 26 (macOS Tahoe). (We already have darwin/arm64 builders with this macOS version as of issue #76798.) This is the very last macOS versio…
Hold for CL 758160 readiness. (To make tracking easier.)
The builder has been added and it's working. For golang/go#26746. For golang/go#77284. Fixes golang/go#26653.
@neild On the main branch, CL 751360 added the mongo-specific implementation and a test, and CL 758900 generalized it for non-http/https and kept the test. The Go 1.26 backport CL 758901 adds the new…
Now that #78323 is resolved, the builder is passing [at tip](https://ci.chromium.org/ui/p/golang/builders/ci/gotip-linux-amd64-longtest-git2.24.0). It's also passing on [release-branch.go1.26](https…
This change is ready for review.
This change is ready for review.
@gopherbot Please consider this for backport to Go 1.25. (Go 1.​26 already has these fixes, so nothing to backport there.) These are test-only fixes needed to make tests pass with the oldest suppor…
Follow-up cleanup on go.dev/cl/698835. Clarify the tests by replacing git-min-vers with a more-purposeful git-sha256 verb in the cmd tests.
Fix test building on older Ubuntu LTS releases (that are still supported). Git SHA256 support was only included in 2.29, which came out in 2021. Check the output of `git version` and skip these tests…
This addition seems reasonable since this code path affects Go developers only. Note that it's untested by builders, so it'll be up to whoever uses it locally to maintain. Thanks. Fixes #nnn? This s…
There have been a number of "internal compiler error" issues reported recently, each covering specific edge cases that were uncovered. This is an umbrella issue to make it easier to track them. CC @…
From triage, it sounds like the redirect happens by an initially trusted source, and not forwarding GOAUTH may cause it to not work for the target. So there may not be any behavior change to do here.
CC @golang/compiler.
From triage, maybe this test doesn't need to run on GOARCH=ppc64le as well. CC @golang/ppc64.
Are you able to reproduce this when using either Go 1.26 or 1.25? In the go env output, it looked like the Go toolchain version was 1.22.
Thanks. The 1.26/1.25 (only) builders failing was [expected](https://go-review.googlesource.com/c/website/+/746741/comments/ae57427c_0909aa7c). The backport CLs have just landed, so everything shoul…
Need to confirm whether 1.25 backport is also needed, or if this is 1.26-only per https://github.com/golang/go/issues/34536#issuecomment-572188389.
Does the problem also affect Go 1.25? In that case we should also backport to 1.25 per our policy.
It passed at tip (https://ci.chromium.org/b/8686347220472067905) and correctly detected a problem intentionally re-introduced in CL 759121, so everything seems working as intended to me. Thanks.
It was missed in CL 737260. For golang/go#43046.
(1 comment) I agree it would be good to update mkwinsyscall to support this use case, and that it can happen later. In the meantime, what do you think about temporarily replacing the need for manual…
Thanks for the report. Does this happen only on the linux/riscv64 port specifically, or are you able to reproduce it on other ports too? CC @golang/riscv64.
dmitshur commented on security: fix CVE-2026-338106d
CC @golang/security, @golang/release.