In case it helps, I've found the following 3 very simple files to work well in my testing. They support both light and dark modes, switching between them based on the OS-wide (or browser-wide) prefer…
Great! Yes, as long as you're taking care of the swarming_bot instance separation carefully as you mentioned and you're not seeing problems as a result of it, reusing a single Linux machine as the pr…
I believe this is the same as issue #26520, except that one is about all of the golang.org/dl/go1.N.M commands, not just the gotip one. In that issue, one of the suggested names for a environment var…
Ok, the [plan9-arm](https://chromium-swarm.appspot.com/bot?id=plan9-arm) bot has the target_ dimensions applied now, and I've submitted [CL 637437](https://go.dev/cl/637437). You should be able to pr…
Ok, we should have a way to move forward. Instead of matching the individual Plan 9 builders for each of the GOARCH values by swarming bot id, which doesn't scale beyond 1 bot, we'll match by new tar…
@rsc The fix pending refers to [CL 633275](https://go.dev/cl/633275) from 2 weeks ago (via https://github.com/golang/go/issues/67450#issuecomment-2515255872 above; you might need to expand timeline).…
To clarify about the release process: while we're in the [freeze](https://groups.google.com/g/golang-dev/c/JkRenbsSBv4) for Go 1.24 now, all changes submitted to the main branch are for the eventual …
Thanks.
I think this is good now, and in the future, if there turns out to be more per-OS cases or this logic needs to be used in more places, this can be factored out into a "supported" helper.
You're doing the "--02" suffix part right, but running into a limitation of the approach we used in https://github.com/golang/go/issues/62025#issuecomment-2135813578 that currently relies on the "id"…
Indeed, thanks!
Optionally, consider switching to using the version.sh helper here:
```suggestion
VERSION := $(shell ../coordinator/version.sh)
```
It provides additional information about the sta…
@kaovilai Thanks. I agree that absent of a toolchain directive, it's viable to pick either exactly the minimum toolchain that meets the 'go' directive requirement, or the latest minor release of the…
I'm not sure I understand that point. The toolchain directive, in contrast to the go directive, applies only to the current module (the one defined by the go.mod file). It suggests the toolchain to b…
The original issue reports:
> 1.22.0 go.mod results in 1.22.0 being used and no option to use later 1.22
I have a question about that – what is the behavior for the following go.mod file:
…
Watchflakes currently implements retries at the process level. That is, it has many code paths that handle errors with a log.Fatal (see [here](https://cs.opensource.google/search?q=fatal&ss=go%2Fx%2F…
Thank you for offering to provide the builders, and apologies for the delay in getting back to these questions.
> Therefore it's hard to get any decent powerful hardware for CI stuff. Should those…
I plan to merge this in a few days. This PR exists so that it's possible to leave review comments before then, but a review is not required. Thanks.
References:
- https://developer.mozilla.org/…
These headings are automatically generated rather than hand-written, and it's likely they got more repetitive after we switched to using Markdown for release notes instead of raw HTML (e.g., issue #6…
We've now set a maintenance window to be during early weekday mornings, skipping Friday. We can wait a bit to see how it goes, adjusting further if needed.
The comment at https://github.com/GoogleCloudPlatform/gsutil/issues/1776#issuecomment-2538018415 says that gsutil version 5.32 and above supports Python 3.12.
Checking in on the status here. Did the comment above resolve the need to make further changes, or would you still like to pursue that?
The builder appears to be missing now (https://ci.chromium.o…
At Go tip, js/wasm programs inside a browser run into a panic during init of syscall package:
```
panic: syscall/js: call of Value.Int on undefined
goroutine 1 [running]:
syscall/js.Value.flo…
There are LUCI builders for netbsd/arm and netbsd/arm64 ports (#63698 and #63614). They're remote, so this change is something their builder owner can consider applying (CC @bsiegert).
I don't believe there are active plans to pursue a non-reverse netbsd/arm64 builder now, and a newer reverse builder for LUCI was added: https://ci.chromium.org/ui/p/golang/builders/luci.golang.ci/go…
[CL 634041](https://go.dev/cl/634041), [CL 631336](https://go.dev/cl/631336), and [CL 626995](https://go.dev/cl/626995) took care of the start-of-freeze updates for the Go 1.24 cycle. There may still…
[CL 612555](https://go.dev/cl/612555) regenerated the list for Go 1.24. It's the same list as for Go 1.23 but without windows/arm (32-bit), and that's noted at https://go.dev/doc/go1.24#windows.
I…
Anything other "pick latest versions of all x/ repos" does need some manual intervention. You could still use updatestd, just followed by a `go get golang.org/x/net@{pseudo-version before CL 632816}`…
Also reproduces on an M1 Pro machine.
> Looking through the code some codepaths sanitize the nanoseconds before calling predictN, others don't. I'll send a fix.
I did that locally (in B.stopOrScale…
Now that #61095 is nearly done, I think this should be a matter of adding the right package to [this line](https://cs.opensource.google/go/x/build/+/master:env/freebsd-amd64/make.bash;l=249;drc=a0b63…
The cmd/relnote test requires that all new APIs have a corresponding entry in doc/next/\*-stdlib/\*-minor. This works as intended for most APIs, but some new APIs are entirely new packages. Those are…
The Go porting policy has a section on broken ports, https://go.dev/wiki/PortingPolicy#broken-ports. The GOOS=windows GOARCH=arm (not arm64) port was marked broken in August 2024 ([CL 601777](https:/…
We considered this freeze exception in a release meeting today. This seems to be a new API that would be safe to land in the next upcoming major Go release, Go 1.25, so that if there are unexpected i…
Thanks for the quick fix! The monthly golang.org/x tagging workflow ran into this, and the fix allowed it to keep going (https://go.googlesource.com/crypto/+/refs/tags/v0.30.0).
At Go tip, TestMultiSign fails when run without -short flag, including on first class ports like linux/amd64:
```
=== RUN TestMultiSign
clearsign_test.go:155: cannot create key: rsa: gener…
Added okay-after-rc1 since RC 1 is scheduled for [next week](https://go.dev/s/release#june--december-week-2-release-candidate-1-issued) and 2024b is still the latest. (CC @mknyszek.) We'll keep this …
@seankhliao I don't see a [frozen notice](https://go.dev/wiki/Frozen) convention applied to golang.org/x/tools/godoc nor golang.org/x/tools/godoc/vfs. It doesn't seem to be frozen? Does that still ne…
In addition to workflows for all of Go release types, relui holds a few workflows for miscellaneous recurring tasks that come up in the release cycle (go.dev/s/release) such as [pinging early-in-cycl…
This issue is still valid and relevant to the package, but the package itself is probably less relevant now that io/fs exists. It should probably be deprecated in favor of that as part of #59056.
By now we have answers to those questions from 6 years ago: removing a golang.org/x package involves deprecating it, isolating it to its own nested module, tagging that, and then deleting from main b…
At tip (commit c5adb8216968be46bd11f7b7360a7c8bde1258d9), TestBenchmarkBLoopIterationCorrect succeeds under most conditions.
<details><br>
```
$ go test -run=^TestBenchmarkBLoopIterationCorrec…
(minor) Oddly, this go-cmp go.mod checksum entry, as well as the xerrors go.mod entry on line 6, do not show up for me after a `go mod tidy` with go1.23.3. But extra lines in go.sum are harmless.
We solved this during the migration to LUCI, golang.org/x/xerrors has post-submit builders visible on its dashboard (e.g., https://ci.chromium.org/p/golang/g/x-xerrors-gotip/console). It's still not …
@mvdan This issue can indeed be marked as closed since it's resolved in Go 1.24, but the Go1.24 milestone is right. There are child backport issues that need to refer to this one. We need a parent is…
This is a continuation of https://github.com/golang/go/issues/69234#issuecomment-2501169320. So far, These particular failures seem to only happen on the darwin/amd64 builders with macOS 11.
A [comment on CL 618601](https://go-review.git.corp.google.com/c/go/+/618601/comments/3d652992_21d045d6) indicated that the change (which fixed #63934 and #68652) should likely be mentioned in [Go 1.…
A [comment on the CL](https://go-review.googlesource.com/c/go/+/618598/comments/6a1b5da8_513f46c7) suggested that this change should be mentioned in [Go 1.24 release notes](https://github.com/golang/…
@neild This change (a package available only when an experiment is set) should be mentioned in [Go 1.24 release notes](https://github.com/golang/go/issues/68545), otherwise users might not know it ex…
This looks like a change that needs to be mentioned in [Go 1.24 release notes](https://github.com/golang/go/issues/68545), is that right? Reopening as a release blocker to track that.
It looks like [CL 630775](https://go.dev/cl/630775) implemented most of this proposal if not all, though it didn't close it. What's left for Go 1.24? Is it just SecP256r1MLKEM768, which according to …
This cmd/go change might be noteworthy enough¹ to be covered in [Go 1.24 release notes](https://github.com/golang/go/issues/68545), so reopening with a release blocker to track that.
¹ In additi…
@rolandshoemaker There's no API change here, but this still seems like a change that should be covered in [Go 1.24 release notes](https://github.com/golang/go/issues/68545), is that right? Mentioning…
@cherrymui Do you think that wasm change (in CL 626615) is something to be mentioned in [Go 1.24 release notes](https://github.com/golang/go/issues/68545)?
@griesemer Do you think there's anything to be said in [Go 1.24 release notes](https://github.com/golang/go/issues/68545) about this? Or is it fine not to mention it there since this a clarification …
This vet change seems like something that needs to be mentioned in [Go 1.24 release notes](https://github.com/golang/go/issues/68545), and it's not mentioned there yet. Reopening as a release blocker…
This looks like a change that needs to be mentioned in [Go 1.24 release notes](https://github.com/golang/go/issues/68545); that doesn't seem to be done yet. Reopening as a release blocker to track th…
A new check added to vet seems like something that needs to be mentioned in [Go 1.24 release notes](https://github.com/golang/go/issues/68545), and it's not mentioned there yet. Reopening as a releas…
This vet change is new to Go 1.24 and still needs to be mentioned in [Go 1.24 release notes](https://github.com/golang/go/issues/68545), right? Reopening with a release blocker label to track that.
This change (enabling these directives in Go 1.24) is documented in cmd/cgo [package docs](https://pkg.go.dev/cmd/cgo@master#hdr-Optimizing_calls_of_C_code), but it seems a note in [Go 1.24 release n…
@ianlancetaylor Do you think this needs to be mentioned in [Go 1.24 release notes](https://github.com/golang/go/issues/68545)? Or should this be considered a minor bug fix on Windows (despite going t…