Yes, in general purple failures are due to something going wrong with the infrastructure, rather than a problem found in the CL. See https://go.dev/wiki/LUCI#infra-failed--purple-failure.
There was …
(1 comment)
A style question: it seems in this case the code would compile both if expected is a variable (as is now) and if it's changed to a `const`. Is there a reason to prefer a variable here ev…
The upstream GLFW issue https://github.com/glfw/glfw/issues/1649 was resolved in GLFW 3.4, and we now have v3.4/glfw package offering that version as of PR #414.
I've re-tested the original report, …
The `MousePassthrough` hint was added in PR #414, and should be available now:
https://pkg.go.dev/github.com/go-gl/glfw/v3.4/glfw#MousePassthrough
Closing as done in commit 8479a9b4422aab8f9d581ef4…
The `MousePassthrough` hint was added in PR #414, and should be available now:
https://pkg.go.dev/github.com/go-gl/glfw/v3.4/glfw#MousePassthrough
Closing as done in commit 8479a9b4422aab8f9d581ef4…
The -u flag was needed back in GOPATH mode to reliably fetch the latest version of the target package and its dependencies. There's no need for it in module mode, since the default [version query](ht…
Thanks very much @alexballas for getting this PR prepared and addressing remaining comments that were left on PR #400. Thank you @Geo25rey for getting PR #400 very far.
I've reviewed and been testin…
(1 comment)
Sounds good. I sent you CL 762720 to fix a broken symlink in the meantime. Tools that try to read all files in this repository (such as 'gcloud builds submit' used during the [deploy pro…
A file containing the expected sha1 for anita-2.10.tar.gz in
the netbsd-386 directory was a symbolic link pointing to the
same file that the netbsd-amd64 directory used to have until
that file was de…
It would've been better to keep the change that re-generates everything with the latest glow and XML files as a separate PR from the change add the OpenGL ES 3.2 support. But they're separate commits…
The change to document Fedora/RHEL-based system requirements seems reasonable. See an inline comment about the other change.
Let's not include this. It wouldn't compile anyway because it doesn't hav…
Thanks.
I'd expect this to be noAlias per https://go.dev/s/style#mixed-caps. Or is it meant to be a single word?
Aside that, maybe it could work well to name the map 'ambiguous' or something like t…
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…
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…
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…
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…
(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…
@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…
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…
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…
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.