Activity

There was a problem fetching the latest activity.

Yesterday
Permission change applied.
This Week
dmitshur fixed an issue os: TestRootRemoveDot failing on Plan 91d
Need to grant the gobot account a permission for the TryBot-Bypass label, since it is being used by it now. Reopening for that.
The `go test` command normally runs a select subset of vet checks, and fails the test if any of them fail. In the main Go repo, to aid development, that behavior is forcibly modified to have all vet…
[CL 678816](https://go.dev/cl/678816) is working, and watchflakes has started posting again. I'll keep an eye on it in the short term, and issue #70743 still remains open to track unexpected restarts.
This issue tracks a remaining subset of the accepted proposal #61716. Specifically: > Once math/rand/v2 has shipped, we would tag and delete x/exp/rand. This would keep programs that already use x/e…
Last Week
Indeed—freeze exceptions would be needed for changes that aren't in scope of the freeze (and ideally they need to be filed and approved before the freeze), but finding and resolving issues in new-t…
Great! I've also updated your email in the approvers group now, so everything should continue to work. Just as a reminder, please be familiar with the rules for voting and submitting changes as desc…
Latest instance fixed in [CL 663975](https://go.dev/cl/663975).
The darwin-arm64-longtest builder is passing at tip and on the Go 1.24 release branch, but it has one failing test on the Go 1.23 release branch. I filed #73922 for it. The darwin-arm64-race builder…
### Go version This affects Go 1.23.x only. The test passes on Go 1.24.x and at tip. ### Output of `go env` in your module/workspace: ```shell GOOS='darwin' GOARCH='arm64' ``` ### What did you do…
The problem appears to be due to a regression in the result_adapter command in [crrev.com/c/6554882](https://crrev.com/c/6554882) from May 19, 2025, which has a pending fix in [crrev.com/c/6598395](h…
The most recent new issue watchflakes opened was #73775 on May 19, 2025. It appears to have gotten almost entirely stuck as of that date, and isn't producing reports. This is the tracking issue. The…
@ysmolski Glad to hear that you were able to update the email in your Gerrit account! It indeed shows up as expected at https://go-review.googlesource.com/dashboard/26536. About the CLA page, in the…
dmitshur commented on access: approvers1w
CC @4a6f656c, @Rongronggg9, @milanknezevic, @mengzhuo Since you're also members of [golang/mips](https://github.com/orgs/golang/teams/mips) and [golang/riscv64](https://github.com/orgs/golang/teams/r…
The current implementation of `constructQuery` is very tailored to the needs of the rest of the graphql package. It doesn't take any options, like the ability to include spaces in formatting, and doe…
Earlier
Since it's not already mentioned here, the proposal for this was #66107, and the accepted plan there was: > The proposal is to allow range over func and int the same as in Go. The current implement…
For clarity, it looks like "Methods and interfaces" was referring to the section title: ![Image](https://github.com/user-attachments/assets/9a4e2ba1-0443-4748-b26b-a3db26d837e0)
[CL 664215](https://go.dev/cl/664215) generated a preliminary list for Go 1.25. It's the same list as for Go 1.24 except the macOS minimum version became 12, and that's noted at https://tip.golang.or…
There isn't anything to pre-announce in Go 1.25 release notes, moving to the next.
There isn't anything to pre-announce in Go 1.25 release notes, moving to the next.
The package requires cgo, so it’s possible to get that error if you’ve disabled cgo. Does anything change if you use CGO_ENABLED=1?
Hello. If you're still able to login to your Gerrit account 26536, you should be able to add and verify a new email (and then make it your new primary preferred email, if desired). The reason you're…
Thanks for addressing this so quickly. I've closed this since the builder is back online and working. If it's useful to have an open issue, we can make a new one.
CC @golang/plan9, @neild.
Perhaps the "not planned" reason is more applicable here, since there was no change.
CC @rolandshoemaker, @FiloSottile.
See https://ci.chromium.org/b/8715046913413654785 for example: ``` === RUN TestObjdumpRISCV64TestDecodeGNUSyntaxdata panic: test timed out after 10m0s running tests: TestObjdumpRISCV64TestDecod…
See https://ci.chromium.org/b/8715046724760256497 for example: ``` === RUN TestMarshalUnmarshal --- FAIL: TestMarshalUnmarshal (0.00s) panic: interface conversion: *sha3.asmState is not encoding.B…
Great, thank you. I think all that's left on our side is to adjust the builder configuration to let the builder run on applicable golang.org/x repositories (it was set to try only the main Go repo w…
Glad to hear that, and congrats on getting to this point! The swarming bot generally takes care of using all of the CPU cores and machine capacity available to it, so the typical setup is to have on…
I've had a chance to talk with Russ about this, and he confirmed that these "go1.8.5rc5" and "go1.9.2rc2" versions aren't really proper Go releases—they're side-effects that happened to be produced…
We've taken the alternative route of making the generated development versions be compatible with the existing https://go.dev/doc/toolchain#name format (as a "non-standard toolchain") in #73372. Is t…
I left some review comments from a quick look, I hope they're helpful. I haven't tried to test the changes locally so I may have missed something. In general, the test seems to be useful, but I th…
This issue has stopped matching because this builder in LUCI no longer has -bsiegert in the name (it's still there in the underlying bot name, but the pattern uses builder name), but there've been so…
The netbsd-amd64-8_0 builder doesn't exist by now, closing.
``` #!watchflakes default <- builder ~ `netbsd-arm64` && "panic: test timed out after 10m0s" ``` Filing this to hopefully catch future instances of issues like #73487, where the underlying problem w…
I believe by now we have resolved the general approach to support Plan 9 testing on LUCI. The plan9 arm and 386 builders seem to be generally working okay for a while now. The amd64 builder seems to …
I'm not sure why this issue was opened 9 hours ago. Given #72857 is now resolved, this should happen only if the builder is dead for 24 hrs, but from looking at [its task history](https://chromium-sw…
Noting that we ran into the same error today. (CC @cherrymui.) The app once again ended up becoming "standalone" for reasons unknown to us. We re-added it to the project.
This is an enhancement to speed up the release process and slightly reduce its resource use, by adding some complexity to its implementation that lets it avoid duplicate work. The Go build system us…
By now the bot is back and idle, having run the last 25+ builds successfully. Not sure that there's anything to do here.
There are currently no bots running at https://ci.chromium.org/ui/p/golang/builders/ci/gotip-openbsd-riscv64. CC @4a6f656c, @golang/riscv64.
There are currently no bots running at https://ci.chromium.org/ui/p/golang/builders/ci/gotip-freebsd-riscv64. CC @mengzhuo, @golang/riscv64.
From looking at the source for those functions ([here](https://source.chromium.org/chromium/infra/infra_superproject/+/main:infra/luci/appengine/swarming/swarming_bot/api/platforms/linux.py?q=%22%5B%…
CC @golang/mips.
@xnox Including additional fields about the toolchain and its possible modifications in the build information (in addition to the go version string) like that is an interesting idea. It has some conn…
It would be good to mention this in Go 1.25 release notes (#71661), otherwise users may not know about it. See [doc/README.md](https://cs.opensource.google/go/go/+/master:doc/README.md).
@seankhliao Can you please clarify what you mean with that comment? Why is this issue closed as not planned?
CC @JunyangShao, @prattmic.
These build failures are fixed via revert CLs above. Closing.
We haven't seen this happen for a while, right? I believe this was a combination of some short-lived builder VMs inadvertently staying around for much longer than intended, and some cache directorie…
It seems to be generally working well. Let's call this done; we can reopen if more is needed.
We'll need to create a backport candidate issue for the Go1.24.3 milestone; moving this to Go1.25.
@srinivas-pokala I believe the change in [crrev.com/c/6439429](https://crrev.com/c/6439429) is rolled out and you should be able to try starting up the builder again.
Fixed by [CL 664495](https://go.dev/cl/664495).
Closed by merging [CL 665856](https://go.dev/cl/665856) (commit golang/build@48b27723f5bd8d92de3f0fff371a73debc7d8feb) to `luci-config`.
The new issue #73405 (CC @prattmic) is a continuation of this, folding this into that.
The new issue #73405 (CC @prattmic) is a continuation of this, folding this into that.
We can try moving the sid builder (#61112) to cos-dev (up from cos-113-lts). If that ends up being too new and too noisy to be useful, we can move down to something less bleeding edge like cos-beta o…
Fixed by [CL 665717](https://go.dev/cl/665717).
Yes, agreed, we should apply this to cmd/dist too. Retitled to capture that too. As for why golangbuild (and coordinator, previously) generates a VERSION file, it does it for a few related reasons: …
It is intended for git-codereview to be available in PATH—see https://go.dev/doc/contribute#git-codereview_install. If you prefer not to add $HOME/go/bin to $PATH, it should still work to place the…
golangbuild currently generates VERSION files with strings like this, a behavior that the Go build system had for a while: ``` devel <commit> devel <change>/<patchset> ``` That satisfies the proper…
The ability to be able to tell that a given Go version isn't a released version can be useful, and quite a bit of code relies on the presence of the "devel" substring as you mentioned. Instead of rem…
I don't think it's viable to rely on manually specifying IDs as in that CL. People will forget to do it in some cases, and changing anchors afterwards on recent release notes might break links.
This umbrella issue is similar to the #60440 umbrella issue, we can merge them together. Closing this one. Thanks everyone.
The build script was updated and a new LUCI-capable image was indeed built, though it's missing python3 (needed for the swarming bot). But we still need to add it to luci-config. Reopening for that.
Yes, there is some similarity to #67468, but it's not the same issue. Over there it is a problem on the side of Gerrit, where for some reason triggering optional trybots doesn't use your primary Gerr…
As seen on the [x/review (gotip) by go commit](https://ci.chromium.org/p/golang/g/x-review-gotip-by-go/console) view, a number of tests have begun to fail starting with [CL 661575](https://go.dev/cl/…
Thanks for reporting. This should be a matter of adding a check for `*noRun` inside `installHook`, before it starts to do `os.Mkdir` and `os.WriteFile`.
Your suggested alternative sounds good. Please go ahead and send the change. One minor suggestion, since that is a complete sentence inside the parentheses, let's also move the period to be inside.
Looks like [CL 637897](https://go.dev/cl/637897) indeed fixed this. Closing, watchflakes will follow up if it still happens.
Thanks for reporting this. The missing builders on those pages are all the new LUCI builders. In #65913 we provided limited support for displaying LUCI build results on build.golang.org, but that su…
The implementation of the check we were using previously is fully gone as of [CL 643916](https://go.dev/cl/643916). I'll close this since the original problem is no longer happening and so the issue …
To connect some dots: in #66009, @mknyszek has a paragraph that mentions a "proxy" builder, which is similar (if not identical) to the "spawning an additional set of builders" description here. At a…