(3 comments)
In the main Go repo, the "src" path element is normally left out, so that the path is closer to the actual import path of the relevant Go package.
```suggestion
cmd/go/internal/doc: al…
(1 comment)
This parent commit is a bit old, before the fix for #80212 landed, so that particular test will fail. Rebasing would resolve that, otherwise we can bypass if that's the only failing test.
(1 comment)
I checked locally that this works with a generic method (that @mpratt@google.com originally reported this with), and it does work as expected:
```
$ go vet -stdversion
main.go:7:19: ran…
Thanks.
I understand this test case, in contrast to the one above, captures the case where it's not a valid version but it does have a valid version as a substring. It seems like a good idea to add …
We removed the release-blocker label since there doesn't seem to be anything actionable left that would block the release. This issue will stay open to track any further refinement and improvement le…
The existing formatting completely forgot to include the
type name T in the name of a field or method pkg.T.name.
Since this cannot be derived from a field *types.Var, we
change TooNewStdSymbols to …
Thanks. 2026c landed in time for Go 1.27.0. It's likely the last tzdata release to be included, so moving this to the next milestone. (If another tzdata release happens with some time before 1.27.0, …
Thanks.
Do you have an opinion on whether an assertion like this should go into test code (i.e., in a _test.go file) or the package implementation code? I have a slight preference for placing these …
Thanks. There are some gopls tests that aren't passing yet.
Is you preference to include this in 1.27's vet output too, or do you think this might be too risky or disruptive and better to leave to G…
It looks like this isn't a regression related to generic methods, rather it's how this check displays methods in general:
<img width="568" height="293" alt="Image" src="https://github.com/user-attac…
@prattmic Thanks. Factored that out into #80363 since it might be more involved, and updated this to be about the more general problem of cmd/vet not being aware of all new-to-1.27 symbols.
For golang/go#38706.
For golang/go#80360.
[git-generate]
go run golang.org/dl/go1.27rc2@latest download
go run golang.org/dl/go1.27rc2@latest generate ./internal/stdlib
For golang/go#38706.
For golang/go#80360.
[git-generate]
go run golang.org/dl/go1.27rc1@latest download
go run golang.org/dl/go1.27rc1@latest generate ./internal/stdlib
(1 comment)
Sounds good. Given we have agreement, we can move in that direction. It can happen independently of this change though, so added it as a TODO comment for now.
Thanks.
Note that this non-nil error is also being returned to the caller to be handled. Adding a log line here will cause it to be double-logged, see line 185.
The new log line includes scanner.Te…
Thanks.
Does it help for this to use $TAG too?
```suggestion
docker run --name=sandbox_dev --rm --network=sandnet -ti -p 127.0.0.1:8080:80/tcp -v /var/run/docker.sock:/var/run/docker.sock golang/p…
Thanks. One more comment in Workflow.Run, otherwise I don't see anything more from my side, and I think you should feel free to submit this and/or try it out. As with any new workflow, trying it out …
Thanks.
```suggestion
module crypto/internal/fips140/sha3/_asm
```
Unrelated to this CL, but I wonder what is the motivation for this go.mod? Usually they're used to track tools used for code gener…
Both the -racegocommand and -racegocommand-noopt builders have been running for some time, and so far they haven't uncovered interesting races in the go command. Issue #79667 turned out to be a probl…
(1 comment)
A question related to this. As far as I see, TOOLEXEC_CDRIVER_LOG is only used to by this test in one way: to point it to a cdriver.log file and then later on check under cgo that it doe…
See https://ci.chromium.org/ui/p/golang/builders/ci/gotip-netbsd-arm64/b8676812685865790769/overview for example. (A different test fails on Plan 9, see #80319.)
CC @golang/netbsd.
We got by with increasing memory available to coordinator. By now it no longer does builds itself, only displays an old-style dashboard [build.golang.org](https://build.golang.org) pointing to [LUCI …
Thanks for implementing this.
I left some review comments. In general, this looks like a good start, and when the comments are resolved we should be able to submit this.
Two suggestions here.
One,…
Thanks.
Since this CL is a part of what's needed, you might want to keep the issue open for a bit until the VMs are up and everything works as you expect.
Unless I missed it, you'll still need to d…
Thanks.
Yeah, I considered that too but stopped at just rc2 for now to match the labels that exist. For rc3 hopefully we'll really resolve all release blockers or remove the release-blocking label. …
Thanks.
I did something similar in CL 732263 earlier. It's still open because I was deciding whether to lower it a bit further before submitting. By now all legacy builds are stopped, so let's go wi…
Generated with updatestd, though it's equivalent to manually running:
cd src/cmd
go get golang.org/x/tools@internal-branch.go1.27-vendor # v0.45.1-0.20260708165844-7044391f8d9f
go mod tidy
go mod v…
Thanks. This looks okay to me so +1, though I expect there may be a better reviewer for go/analysis/passes packages. I understand this will be waiting on the proposal to be accepted anyway.
It took …
This change gets the [golang.org/x/tools/go/analysis/passes/printf.Test](https://ci.chromium.org/ui/p/golang/builders/try/x_tools-go1.27-linux-amd64-longtest/b8676896302437009505/test-results?q=Ex…
This change gets the [golang.org/x/tools/go/ssa.TestStdlib](https://ci.chromium.org/ui/p/golang/builders/try/x_tools-go1.27-linux-amd64-longtest/b8676896325792242385/test-results?q=ExactID%3Agolan…
CL 784060 updates Types.Info.Instantiations to preserve receivers
for generic methods, which breaks these tests. This change updates
a test to allow that CL to merge.
For golang/go#79657.
Fixes gola…
The `internal-branch.go1.27-vendor` branch in x/tools was created quite early after the start of the Go 1.27 release freeze, as opposed to closer to when the Go 1.27 release freeze will be ending. So…
(1 comment)
Since this is a release-branch.go1.26 backport CL, it would've been optimal if the commit message had:
```suggestion
For #79005.
Fixes #79027.
```
Then the Go1.26.5 backport issue #790…
> I investigated this issue and found that updating "pkgsiteCmdInternalDocVersion" to "v0.0.0-20260630164626-55ca6a10dee5" fixes the generic method rendering problem. I verified that "go doc -http" n…
Thanks.
I take it that it's guaranteed that calling t.TempDir() first, and t.Cleanup second will cause the cleanup to run first, TempDir deletion second, right?
Is it intentional that removeAll not…
### Go version
go version go1.27rc1 darwin/arm64
### Output of `go env` in your module/workspace:
(`go env -changed` is empty.)
### What did you do?
```
$ export GOCACHE=$(mktemp -d)
$ go…
Thanks.
Optional suggestion. Since the swarming gomotes are all that's left in the golang.org/x/build/internal/gomote package, consider appending helper.go to the bottom of swarming.go, and renaming…
Thanks.
This test case appears to be hard to read because of how it combines the terms "other", "jsonv2", and "archive/tar" that seemingly have little in common. As a result it's unclear what it's t…
We've created an okay-after-rc2 label, which works like okay-after-rc1
but for RC 2 instead of RC 1. Make the 'Check blocking issues' task more
useful by having it ask only about release blockers tha…
(1 comment)
@neal@golang.org Do you think we should keep this version syntax as is, or is it worth considering making it match the https://go.dev/doc/toolchain#name? I understand that VulnDB needs t…
@matloob Thanks for marking this as done.
The release note currently says "[GOEXPERIMENT=nosizespecializedmalloc] is expected to be removed in Go 1.28."; is there an issue to track doing the work of…
> 👋 Hi! Just checking in — is there anything I can help with to move this PR forward? Happy to address any feedback! 🙏
See https://github.com/golang/website/pull/359#issuecomment-463983711…
The legacy builders have been fully stopped and don't work anymore.
The documentation for them is obsolete and misleading. Remove it.
For golang/go#67761.
The legacy slowbot infrastructure is unsupported and doesn't work. I added their LUCI counterparts as advisory slowbots to this CL:
- [gotip-linux-riscv64](https://ci.chromium.org/ui/p/golang/builde…
There is a [openbsd-riscv64-jsing](https://chromium-swarm.appspot.com/bot?id=openbsd-riscv64-jsing) builder now, but it's showing up as offline as of 24 hrs ago. CC @4a6f656c.
I think I understand this at a high level and it's mostly a refactor. However, I'm not familiar with go command's action caching and coverage instrumentation, so my review isn't going to be very thor…
Thanks.
Consider passing in the *testing.T here and call t.Fatal instead. Also below.
`l` is never closed, even after the test completes. Is the reason for that because the test executable is deeme…
Thanks.
This copy of scripttest is internal to the cmd module, so it makes sense to modify it to suit the needs of all of its internal users. I agree it seems calling removeAll to clean up after the…
Thanks.
I think this is saying that the test is being skipped because it has a 'skip' verb. It's fine, though a bit repetitive.
[go.dev/issue/54043](https://go.dev/issue/54043) is closed, and it's …
As noted in the comment above, closing as fixed by [CL 788222](https://go.dev/cl/788222) which is included in x/crypto@v0.53.0. (CC @golang/security.)
> although the problem is the scan engine
It s…
Thanks.
I left a suggestion to consider including at least one "For #nnn." line. That suggestion is for all CLs in this stack, but I won't repeat it everywhere.
Whenever there's a large stack of CL…
Thanks. Just a minor comment/question.
I don't know what's the motivation to defer base.ExitIfErrors() here given it's already being called on line 1495, and there aren't any early returns before th…