runtime:cpu1: TestLockRankGenerated failures

[gopherbot]

#!watchflakes
default <- pkg == "runtime:cpu1" && test == "TestLockRankGenerated"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestLockRankGenerated
    lockrank_test.go:22: C:\b\s\w\ir\x\w\goroot\bin\go.exe run mklockrank.go: exit status 1
        fork/exec C:\b\s\w\ir\x\w\gocache\2d\2d880d9d593a2ac7e3a0097bd5c02c14293d2fbebb5fa81cd6f30d069ab66557-d\mklockrank.exe: The process cannot access the file because it is being used by another process.
--- FAIL: TestLockRankGenerated (0.48s)

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime:cpu1" && test == "TestLockRankGenerated"

2024-12-11 23:40 go1.24-windows-amd64-longtest release-branch.go1.24@0ca521f9 runtime:cpu1.TestLockRankGenerated (log)

=== RUN   TestLockRankGenerated
    lockrank_test.go:22: C:\b\s\w\ir\x\w\goroot\bin\go.exe run mklockrank.go: exit status 1
        fork/exec C:\b\s\w\ir\x\w\gocache\2d\2d880d9d593a2ac7e3a0097bd5c02c14293d2fbebb5fa81cd6f30d069ab66557-d\mklockrank.exe: The process cannot access the file because it is being used by another process.
--- FAIL: TestLockRankGenerated (0.48s)

— watchflakes

[ianlancetaylor]

On a Unix system this would look like an instance of #22315. Not sure if Windows has any such issues, though.

[mknyszek]

This is probably an issue with multiple tests trying to build/run the same executable, given that this is a go run test. It's probably not multiple runtime package tests because this is an instance of the runtime tests being run with -cpu=1, and on top of that, the test does not run in parallel with other tests. Maybe multiple parallel copies of the runtime package test being run by dist?

@samthanawalla Are there known issues with go run being run by multiple binaries on the same file? Thanks.