runtime/pprof: TestVMInfo failures

[gopherbot]

#!watchflakes
default <- pkg == "runtime/pprof" && test == "TestVMInfo"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestVMInfo
    vminfo_darwin_test.go:97: vmmap output: 
    vminfo_darwin_test.go:99: /usr/bin/vmmap 83423: exit status 255
        vmmap[84999]: No process corpse slots currently available - waiting to get one
        vmmap[84999]: [fatal] Failed to generate corpse: no corpse slots are available
    vminfo_darwin_test.go:105: /usr/bin/vmmap 83423: exit status 255
    vminfo_darwin_test.go:40: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (15.58s)

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime/pprof" && test == "TestVMInfo"

2025-04-22 18:01 gotip-darwin-arm64_15 go@8a85a2e7 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    vminfo_darwin_test.go:97: vmmap output: 
    vminfo_darwin_test.go:99: /usr/bin/vmmap 83423: exit status 255
        vmmap[84999]: No process corpse slots currently available - waiting to get one
        vmmap[84999]: [fatal] Failed to generate corpse: no corpse slots are available
    vminfo_darwin_test.go:105: /usr/bin/vmmap 83423: exit status 255
    vminfo_darwin_test.go:40: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (15.58s)

— watchflakes

[mknyszek]

This was fixed in #62352, but the new Darwin builders (running macOS 15) seem to have trouble with it now.

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime/pprof" && test == "TestVMInfo"

2025-05-12 16:07 gotip-darwin-amd64_14 go@238d273d runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    vminfo_darwin_test.go:86: vmmap taking too long
    exec.go:230: command was started, but test did not wait for it to complete: /usr/bin/vmmap 11004
--- FAIL: TestVMInfo (60.01s)

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime/pprof" && test == "TestVMInfo"

2025-05-13 19:26 gotip-darwin-amd64-nocgo go@afd6b0bc runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    vminfo_darwin_test.go:86: vmmap taking too long
    exec.go:230: command was started, but test did not wait for it to complete: /usr/bin/vmmap 41595
--- FAIL: TestVMInfo (60.01s)

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime/pprof" && test == "TestVMInfo"

2025-05-13 21:03 gotip-darwin-amd64-longtest go@c44c4de5 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    vminfo_darwin_test.go:86: vmmap taking too long
    exec.go:230: command was started, but test did not wait for it to complete: /usr/bin/vmmap 67314
--- FAIL: TestVMInfo (60.01s)

2025-05-13 22:43 gotip-darwin-amd64_14 go@9e026bf9 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    vminfo_darwin_test.go:86: vmmap taking too long
    exec.go:230: command was started, but test did not wait for it to complete: /usr/bin/vmmap 45730
--- FAIL: TestVMInfo (60.00s)

— watchflakes