runtime/pprof: TestVMInfo failures #62352

gopherbot · 2023-08-29T17:41:43Z

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

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestVMInfo (0.37s)
    vminfo_darwin_test.go:59: exit status 255

— watchflakes

The text was updated successfully, but these errors were encountered:

gopherbot · 2023-08-29T17:41:44Z

Found new dashboard test flakes for:

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

2023-08-29 16:16 darwin-amd64-nocgo go@4e48e467 runtime/pprof.TestVMInfo (log)

--- FAIL: TestVMInfo (0.37s)
    vminfo_darwin_test.go:59: exit status 255

— watchflakes

bcmills · 2023-08-29T19:20:38Z

This test is new during the Go 1.22 cycle (https://go.dev/cl/503919; attn @cosnicolaou @cherrymui).

A good starting point would probably be to update the test to log the Stderr field of the *exec.ExitError on failure:
https://cs.opensource.google/go/go/+/master:src/runtime/pprof/vminfo_darwin_test.go;l=59;drc=fdc9cf3c3aaf779387f0341125680f018e5f0275

cosnicolaou · 2023-08-29T21:38:51Z

Ok, see https://go-review.googlesource.com/c/go/+/524156

gopherbot · 2023-08-29T21:38:56Z

Change https://go.dev/cl/524156 mentions this issue: runtime/pprof: print stderr on test failure

Print Stderr on test failure to track down the intermittent test failure reported in issue #62352. Change-Id: I547a3220dc07d05578dac093d6c028a9103b552a Reviewed-on: https://go-review.googlesource.com/c/go/+/524156 Reviewed-by: Michael Knyszek <mknyszek@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>

bcmills · 2023-09-05T12:43:57Z

The new logging is in place, so I've marked this WaitingForInfo to see what turns up after https://go.dev/cl/524936.

gopherbot · 2023-09-08T21:22:50Z

Found new dashboard test flakes for:

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

2023-09-08 20:37 darwin-arm64-11 go@a742ae49 runtime/pprof.TestVMInfo (log)

--- FAIL: TestVMInfo (0.29s)
    vminfo_darwin_test.go:61: vmmap failed: Process:         pprof.test [15435]
        Path:            /private/tmp/*/pprof.test
        Load Address:    0x100f50000
        Identifier:      pprof.test
        Version:         ???
        Code Type:       ARM64
        Parent Process:  go [15399]

        Date/Time:       2023-09-08 16:41:16.280 -0400
...
        ===========                     ======= ========    =====  ======= ========   ======    =====  ======= 
        TOTAL                              2.1G   326.5M    16.0M       0K       0K       0K       0K      355 

                                         VIRTUAL   RESIDENT      DIRTY    SWAPPED ALLOCATION      BYTES DIRTY+SWAP          REGION
        MALLOC ZONE                         SIZE       SIZE       SIZE       SIZE      COUNT  ALLOCATED  FRAG SIZE  % FRAG   COUNT
        ===========                      =======  =========  =========  =========  =========  =========  =========  ======  ======
        DefaultMallocZone_0x10129c000      9216K        64K        64K         0K        209        11K        53K     83%       2

    vminfo_darwin_test.go:63: /usr/bin/vmmap 15435: exit status 255
        vmmap[15527]: [fatal]  child process status could not be determined; exit code unavailable.

— watchflakes

cosnicolaou · 2023-09-11T16:03:54Z

ok, I see what's going on, and I'll provide a workaround, hopefully today.

…

On Fri, Sep 8, 2023 at 2:23 PM GopherBot ***@***.***> wrote: Found new dashboard test flakes for: #!watchflakes default <- pkg == "runtime/pprof" && test == "TestVMInfo" 2023-09-08 20:37 darwin-arm64-11 ***@***.*** runtime/pprof.TestVMInfo (log <https://build.golang.org/log/3523f6558165872a1370b4ab3ad56c301b91c576>) --- FAIL: TestVMInfo (0.29s) vminfo_darwin_test.go:61: vmmap failed: Process: pprof.test [15435] Path: /private/tmp/*/pprof.test Load Address: 0x100f50000 Identifier: pprof.test Version: ??? Code Type: ARM64 Parent Process: go [15399] Date/Time: 2023-09-08 16:41:16.280 -0400 ... =========== ======= ======== ===== ======= ======== ====== ===== ======= TOTAL 2.1G 326.5M 16.0M 0K 0K 0K 0K 355 VIRTUAL RESIDENT DIRTY SWAPPED ALLOCATION BYTES DIRTY+SWAP REGION MALLOC ZONE SIZE SIZE SIZE SIZE COUNT ALLOCATED FRAG SIZE % FRAG COUNT =========== ======= ========= ========= ========= ========= ========= ========= ====== ====== DefaultMallocZone_0x10129c000 9216K 64K 64K 0K 209 11K 53K 83% 2 vminfo_darwin_test.go:63: /usr/bin/vmmap 15435: exit status 255 vmmap[15527]: [fatal] child process status could not be determined; exit code unavailable. — watchflakes <https://go.dev/wiki/Watchflakes> — Reply to this email directly, view it on GitHub <#62352 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACCMUYHUML7VEDBTEBIHNFDXZOEDPANCNFSM6AAAAAA4DJ3CZM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

gopherbot · 2023-09-11T18:30:19Z

Change https://go.dev/cl/527276 mentions this issue: runtime/pprof: TestVMInfo reworked to avoid test flakiness.

cosnicolaou · 2023-09-11T18:30:19Z

See #527276

gopherbot · 2023-10-25T15:05:02Z

Found new dashboard test flakes for:

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

2023-10-18 14:46 darwin-amd64-12_0 go@1ec427e7 runtime/pprof.TestVMInfo (log)

--- FAIL: TestVMInfo (0.52s)
    vminfo_darwin_test.go:62: vmmap output: 
    vminfo_darwin_test.go:64: /usr/bin/vmmap 10392: exit status 255
        vmmap[10478]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:66: /usr/bin/vmmap 10392: exit status 255
    vminfo_darwin_test.go:74: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found

— watchflakes

cosnicolaou · 2023-10-25T17:18:45Z

Well, I'm not sure what to do about this, since it looks as if the CI runner doesn't have the resources to run another subprocess given the error message vmmap[10478]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting What would you suggest? There is no other way of testing this functionality other than comparing the values that the runtime generates with the values that the OS would generate. I'm open to suggestions!

gopherbot · 2023-11-08T16:17:08Z

Found new dashboard test flakes for:

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

2023-11-08 14:13 darwin-amd64-12_0 go@8fb8d0df runtime/pprof.TestVMInfo (log)

--- FAIL: TestVMInfo (0.39s)
    vminfo_darwin_test.go:62: vmmap output: 
    vminfo_darwin_test.go:64: /usr/bin/vmmap 10481: exit status 255
        vmmap[10563]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:66: /usr/bin/vmmap 10481: exit status 255
    vminfo_darwin_test.go:74: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found

— watchflakes

bcmills · 2023-11-08T16:20:52Z

@cosnicolaou, at the very least, perhaps the test should skip instead of failing if the output matches that failure mode.

cosnicolaou · 2024-03-12T18:43:22Z

Hi Bryan,

I see that this is persisting. Is it a problem with the CI runners or should I disable this test?

Cheers, Cos.

gopherbot · 2024-03-19T14:47:20Z

Found new dashboard test flakes for:

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

2024-03-19 11:31 darwin-amd64-nocgo go@d14cf8f9 runtime/pprof.TestVMInfo (log)

--- FAIL: TestVMInfo (173.53s)
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 10309: exit status 255
        vmmap[10337]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 10309: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 10309: exit status 255
        vmmap[10338]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 10309: exit status 255
...
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 10309: exit status 255
        vmmap[10876]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 10309: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    exec.go:193: test timed out while running command: /usr/bin/vmmap 10309
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 10309: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found

— watchflakes

cherrymui · 2024-03-19T15:44:33Z

@cosnicolaou as the "resource shortage" seems to be persistent, not really temporary (at least within the duration of the test execution), it is probably okay to skip the test when such an error is seen. Apple tools are known to be somewhat flaky...

gopherbot · 2024-03-22T21:02:26Z

Found new dashboard test flakes for:

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

2024-03-21 00:10 gotip-darwin-amd64_12 go@7d4d71e5 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 8733: exit status 255
        vmmap[9161]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 8733: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 8733: exit status 255
        vmmap[9168]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 8733: exit status 255
...
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 8733: exit status 255
        vmmap[39420]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 8733: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    exec.go:193: test timed out while running command: /usr/bin/vmmap 8733
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 8733: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (533.18s)

2024-03-21 00:52 gotip-darwin-amd64-longtest go@36cd8808 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 25266
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 25266: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (2360.30s)

2024-03-21 00:52 gotip-darwin-amd64_14 go@36cd8808 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 22128
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 22128: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (474.09s)

2024-03-21 09:16 gotip-darwin-amd64_14 go@dc0527ee runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 30502
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 30502: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (476.96s)

2024-03-21 09:27 gotip-darwin-amd64-nocgo go@0a0758af runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 11042
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 11042: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (480.37s)

2024-03-21 09:29 gotip-darwin-amd64-longtest go@f2685395 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 12022
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 12022: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (2344.21s)

2024-03-21 11:49 gotip-darwin-amd64-longtest go@68a508cd runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 9227
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 9227: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (2359.03s)

2024-03-21 11:49 gotip-darwin-amd64-nocgo go@cff7267e runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 52617
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 52617: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (479.83s)

2024-03-21 16:12 gotip-darwin-amd64_12 go@d9f97467 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 34245: exit status 255
        vmmap[34724]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 34245: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 34245: exit status 255
        vmmap[34730]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 34245: exit status 255
...
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 34245: exit status 255
        vmmap[65108]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 34245: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    exec.go:193: test timed out while running command: /usr/bin/vmmap 34245
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 34245: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (532.34s)

2024-03-21 16:12 gotip-darwin-amd64_14 go@d9f97467 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 41997
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 41997: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (474.73s)

— watchflakes

gopherbot · 2024-04-03T00:35:50Z

Found new dashboard test flakes for:

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

2024-04-02 21:51 darwin-amd64-nocgo go@d08a9572 runtime/pprof.TestVMInfo (log)

--- FAIL: TestVMInfo (173.97s)
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 10409: exit status 255
        vmmap[10434]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 10409: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 10409: exit status 255
        vmmap[10436]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 10409: exit status 255
...
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 10409: exit status 255
        vmmap[10935]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:84: /usr/bin/vmmap 10409: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    exec.go:193: test timed out while running command: /usr/bin/vmmap 10409
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 10409: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found

— watchflakes

gopherbot · 2024-04-16T13:45:19Z

Change https://go.dev/cl/579295 mentions this issue: runtime/pprof: test for Darwin flake in TestVMInfo

If it contains "No process corpse slots currently available, waiting to get one" skip the test in short mode, so that run.bash works reliably on developer laptops, but the flake is still recorded on builders. The problem also seems to get better after a laptop reboot? Updates #62352. Change-Id: I12e8f594f0b830bacda5d8bfa594782345764c4a Reviewed-on: https://go-review.googlesource.com/c/go/+/579295 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Cherry Mui <cherryyz@google.com>

gopherbot · 2024-04-18T21:52:51Z

Found new dashboard test flakes for:

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

2024-03-21 17:29 go1.22-darwin-amd64-nocgo release-branch.go1.22@35b1a146 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 28730
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:84: /usr/bin/vmmap 28730: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (479.91s)

2024-04-18 15:41 gotip-darwin-amd64_14 go@a973b425 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 36194
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:87: /usr/bin/vmmap 36194: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (475.85s)

— watchflakes

gopherbot · 2024-04-19T17:44:52Z

Found new dashboard test flakes for:

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

2024-04-19 16:55 gotip-darwin-amd64_12 go@f0d6ddfa runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 72460: exit status 255
        vmmap[72792]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:87: /usr/bin/vmmap 72460: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 72460: exit status 255
        vmmap[72796]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:87: /usr/bin/vmmap 72460: exit status 255
...
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:81: /usr/bin/vmmap 72460: exit status 255
        vmmap[3856]: [fatal] Failed to generate corpse from the process: 6 ((os/kern) resource shortage), exiting
    vminfo_darwin_test.go:87: /usr/bin/vmmap 72460: exit status 255
    vminfo_darwin_test.go:69: retrying vmmap after error: exit status 255
    exec.go:193: test timed out while running command: /usr/bin/vmmap 72460
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:87: /usr/bin/vmmap 72460: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (534.30s)

— watchflakes

gopherbot · 2024-04-19T20:45:46Z

Found new dashboard test flakes for:

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

2024-04-19 17:39 gotip-darwin-amd64_14 go@c260de24 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 17259
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:87: /usr/bin/vmmap 17259: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (475.02s)

— watchflakes

gopherbot · 2024-04-22T15:44:40Z

Found new dashboard test flakes for:

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

2024-04-22 13:29 gotip-darwin-amd64-longtest go@2dddc7ef runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 62841
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:87: /usr/bin/vmmap 62841: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (2346.21s)

— watchflakes

gopherbot · 2024-04-22T16:44:55Z

Found new dashboard test flakes for:

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

2024-04-22 14:55 gotip-darwin-amd64_14 go@69aa1974 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:193: test timed out while running command: /usr/bin/vmmap 68865
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:87: /usr/bin/vmmap 68865: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (475.69s)

— watchflakes

gopherbot · 2024-10-21T16:15:23Z

Found new dashboard test flakes for:

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

2024-10-21 13:40 gotip-darwin-amd64_14 go@c0a126b8 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:213: test timed out while running command: /usr/bin/vmmap 45638
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:87: /usr/bin/vmmap 45638: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (467.47s)

— watchflakes

gopherbot · 2024-10-21T18:15:24Z

Found new dashboard test flakes for:

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

2024-10-21 15:56 gotip-darwin-amd64-nocgo go@a1c4fb43 runtime/pprof.TestVMInfo (log)

=== RUN   TestVMInfo
    exec.go:213: test timed out while running command: /usr/bin/vmmap 17751
    vminfo_darwin_test.go:79: vmmap output: 
    vminfo_darwin_test.go:87: /usr/bin/vmmap 17751: signal: quit
    vminfo_darwin_test.go:39: failed to parse vmmap output, vmmap reported an error: vmmap no text segment found
--- FAIL: TestVMInfo (956.97s)

— watchflakes

mknyszek · 2024-11-13T21:23:33Z

In triage, we're thinking this is actually due to some problems with the tool provided by Apple, and maybe we should just wrap it in retries.

cosnicolaou · 2024-11-13T23:40:03Z

see https://go-review.googlesource.com/c/go/+/560935

…

On Wed, Nov 13, 2024 at 1:23 PM Michael Knyszek ***@***.***> wrote: In triage, we're thinking this is actually due to some problems with the tool provided by Apple, and maybe we should just wrap it in retries. — Reply to this email directly, view it on GitHub <#62352 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACCMUYF4NYA5HJMSEWRN2FT2AO7O3AVCNFSM6AAAAAA4DJ3CZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZUHAYTENZXGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

cherrymui · 2024-11-14T14:56:07Z

@cosnicolaou thanks. Does the CL fix the failures? If so, maybe rebase and get it submitted (it has a merge conflict)? Thanks.

cosnicolaou · 2024-11-15T21:36:31Z

I've updated the PR to fix the merge conflict.

…

On Thu, Nov 14, 2024 at 6:56 AM cherrymui ***@***.***> wrote: @cosnicolaou <https://github.com/cosnicolaou> thanks. Does the CL fix the failures? If so, maybe rebase and get it submitted (it has a merge conflict)? Thanks. — Reply to this email directly, view it on GitHub <#62352 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACCMUYGKZXH4UD6KOPGAEHL2AS2Z7AVCNFSM6AAAAAA4DJ3CZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZWGU4DGMBQGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Aug 29, 2023

gopherbot added this to Test Flakes Aug 29, 2023

gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Aug 29, 2023

mknyszek added this to Go Compiler / Runtime Aug 30, 2023

mknyszek moved this to Todo in Go Compiler / Runtime Aug 30, 2023

mknyszek moved this from Todo to In Progress in Go Compiler / Runtime Aug 30, 2023

mknyszek added this to the Backlog milestone Aug 30, 2023

bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Sep 5, 2023

bcmills added WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. and removed WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Sep 5, 2023

bcmills removed the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Sep 8, 2023

gopherbot closed this as completed in 7d0b611 Sep 14, 2023

github-project-automation bot moved this from In Progress to Done in Go Compiler / Runtime Sep 14, 2023

github-project-automation bot moved this to Done in Test Flakes Sep 14, 2023

gopherbot reopened this Oct 25, 2023

github-project-automation bot moved this from Done to In Progress in Go Compiler / Runtime Oct 25, 2023

gopherbot modified the milestones: Go1.23, Go1.24 Aug 13, 2024

mknyszek moved this from In Progress to Todo in Go Compiler / Runtime Nov 13, 2024

mknyszek modified the milestones: Go1.24, Backlog Nov 13, 2024

gopherbot closed this as completed in 8ac0a7c Nov 16, 2024

github-project-automation bot moved this from Todo to Done in Go Compiler / Runtime Nov 16, 2024

dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Nov 19, 2024

dmitshur modified the milestones: Backlog, Go1.24 Nov 19, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

runtime/pprof: TestVMInfo failures #62352

runtime/pprof: TestVMInfo failures #62352

gopherbot commented Aug 29, 2023 •

edited by cherrymui

Loading

gopherbot commented Aug 29, 2023

bcmills commented Aug 29, 2023

cosnicolaou commented Aug 29, 2023

gopherbot commented Aug 29, 2023

bcmills commented Sep 5, 2023

gopherbot commented Sep 8, 2023

cosnicolaou commented Sep 11, 2023 via email

gopherbot commented Sep 11, 2023

cosnicolaou commented Sep 11, 2023

gopherbot commented Oct 25, 2023

cosnicolaou commented Oct 25, 2023

gopherbot commented Nov 8, 2023

bcmills commented Nov 8, 2023

cosnicolaou commented Mar 12, 2024

gopherbot commented Mar 19, 2024

cherrymui commented Mar 19, 2024

gopherbot commented Mar 22, 2024

gopherbot commented Apr 3, 2024

gopherbot commented Apr 16, 2024

gopherbot commented Apr 18, 2024

gopherbot commented Apr 19, 2024

gopherbot commented Apr 19, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Oct 21, 2024

gopherbot commented Oct 21, 2024

mknyszek commented Nov 13, 2024

cosnicolaou commented Nov 13, 2024 via email

cherrymui commented Nov 14, 2024

cosnicolaou commented Nov 15, 2024 via email

runtime/pprof: TestVMInfo failures #62352

runtime/pprof: TestVMInfo failures #62352

Comments

gopherbot commented Aug 29, 2023 • edited by cherrymui Loading

gopherbot commented Aug 29, 2023

bcmills commented Aug 29, 2023

cosnicolaou commented Aug 29, 2023

gopherbot commented Aug 29, 2023

bcmills commented Sep 5, 2023

gopherbot commented Sep 8, 2023

cosnicolaou commented Sep 11, 2023 via email

gopherbot commented Sep 11, 2023

cosnicolaou commented Sep 11, 2023

gopherbot commented Oct 25, 2023

cosnicolaou commented Oct 25, 2023

gopherbot commented Nov 8, 2023

bcmills commented Nov 8, 2023

cosnicolaou commented Mar 12, 2024

gopherbot commented Mar 19, 2024

cherrymui commented Mar 19, 2024

gopherbot commented Mar 22, 2024

gopherbot commented Apr 3, 2024

gopherbot commented Apr 16, 2024

gopherbot commented Apr 18, 2024

gopherbot commented Apr 19, 2024

gopherbot commented Apr 19, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Oct 21, 2024

gopherbot commented Oct 21, 2024

mknyszek commented Nov 13, 2024

cosnicolaou commented Nov 13, 2024 via email

cherrymui commented Nov 14, 2024

cosnicolaou commented Nov 15, 2024 via email

gopherbot commented Aug 29, 2023 •

edited by cherrymui

Loading