New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runtime/pprof: TestVMInfo failures #62352
Comments
Found new dashboard test flakes for:
2023-08-29 16:16 darwin-amd64-nocgo go@4e48e467 runtime/pprof.TestVMInfo (log)
|
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 |
Change https://go.dev/cl/524156 mentions this issue: |
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>
The new logging is in place, so I've marked this WaitingForInfo to see what turns up after https://go.dev/cl/524936. |
Found new dashboard test flakes for:
2023-09-08 20:37 darwin-arm64-11 go@a742ae49 runtime/pprof.TestVMInfo (log)
|
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:
***@***.***>
|
Change https://go.dev/cl/527276 mentions this issue: |
Found new dashboard test flakes for:
2023-10-18 14:46 darwin-amd64-12_0 go@1ec427e7 runtime/pprof.TestVMInfo (log)
|
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 |
Found new dashboard test flakes for:
2023-11-08 14:13 darwin-amd64-12_0 go@8fb8d0df runtime/pprof.TestVMInfo (log)
|
@cosnicolaou, at the very least, perhaps the test should skip instead of failing if the output matches that failure mode. |
That's a reasonable suggestion, but I'd worry that the test could fail
silently for extended periods and hence be rendered useless without us ever
knowing. Similarly, I could retry the test, but that seems like the wrong
thing to do on an overloaded test runner. Was this the only test run that
failed at that time on that runner - i.e. was the runner sufficiently
overloaded for other tests to fail? Has it happened again/how often does it
happen?
Anyway, I'd be happy to make the change, but I'm not sure it's solving a
problem beyond having a clean dashboard. Consider that if every test took
this approach then they could all be failing because of an
overloaded/broken runner and we'd think everything was in good shape!
Cheers, Cos.
…On Wed, Nov 8, 2023 at 8:21 AM Bryan C. Mills ***@***.***> wrote:
@cosnicolaou <https://github.com/cosnicolaou>, at the very least, perhaps
the test should skip instead of failing if the output matches that failure
mode.
—
Reply to this email directly, view it on GitHub
<#62352 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCMUYHM5NR2OSWQGC6HO7TYDOWPFAVCNFSM6AAAAAA4DJ3CZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSGIZDQNZQHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Agreed; that's a problem for flaky tests in general. Making the skip as precise as possible helps somewhat (it prevents the skip from masking other failures), but it would still be possible for the test to skip due to this exact failure mode unexpectedly.
I agree that a retry is unfortunate, but it might be the least-bad option. It seems better to waste a small amount of resources on retrying a single test, instead of wasting a much larger amount of resources retrying an entire failed TryBot run or causing a contributor to have to re-run
At least in the last log that was posted, no other tests failed. Note that the Go runtime explicitly retries The history of that retry seems to be related to #18146, in which calling
The logs posted on this issue are the failures I am aware of.
Alert fatigue is a problem in its own right: if we train people that test failures are just something that occasionally happens in normal operation, then they will dismiss intermittent test failures that may indicate a deeper, systematic problem. (In the case of macOS in particular, we currently have #63937 and #60449 to contend with on that front.) |
OK, so if I read your note correctly, the suspicion is that the runner is
not actually overloaded, but rather, it's a case of 18146. This seems at
least plausible to me if there were no other issues with the test runner
when this test failed. I'll make the test retry when it sees this error
rather than skipping.
Cheers, Cos.
…On Wed, Nov 8, 2023 at 8:58 AM Bryan C. Mills ***@***.***> wrote:
I'd worry that the test could fail silently for extended periods and hence
be rendered useless without us ever
knowing
Agreed; that's a problem for flaky tests in general. Making the skip as
precise as possible helps somewhat (it prevents the skip from masking other
failures), but it would still be possible for the test to skip due to this
exact failure mode unexpectedly.
I could retry the test, but that seems like the wrong thing to do on an
overloaded test runner.
I agree that a retry is unfortunate, but it might be the least-bad option.
It seems better to waste a small amount of resources on retrying a single
test, instead of wasting a much larger amount of resources retrying an
entire failed TryBot run or causing a contributor to have to re-run go
test (or, even worse, all.bash) after a spurious failure on their local
machine.
Was this the only test run that failed at that time on that runner - i.e.
was the runner sufficiently
overloaded for other tests to fail?
At least in the last log that was posted, no other tests failed.
Note that the Go runtime explicitly retries EAGAIN errors from
pthread_create, which seems likely to stem from essentially the same
resource exhaustion problem:
https://cs.opensource.google/go/go/+/master:src/runtime/os_darwin.go;l=244-246;drc=4be921d888d3a68c51e38d4c615a4438c7b2cb30
The history of that retry seems to be related to #18146
<#18146>, in which calling
pthread_create concurrently with exec caused a spurious EAGAIN error.
Perhaps the error in vmmap could have a related cause?
Has it happened again/how often does it happen?
The logs posted on this issue are the failures I am aware of.
I'd be happy to make the change, but I'm not sure it's solving a problem
beyond having a clean dashboard.
Alert fatigue <https://en.wikipedia.org/wiki/Alarm_fatigue> is a problem
in its own right: if we train people that test failures are just something
that occasionally happens in normal operation, then they will dismiss
intermittent test failures that may indicate a deeper, systematic problem.
(In the case of macOS in particular, we currently have #63937
<#63937> and #60449
<#60449> to contend with on that
front.)
—
Reply to this email directly, view it on GitHub
<#62352 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCMUYBEXYEU5XLAQC7ZVTLYDO233AVCNFSM6AAAAAA4DJ3CZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSGI4TGNRXHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I just mailed a CL for this, sorry for the delay! |
Change https://go.dev/cl/545935 mentions this issue: |
Found new dashboard test flakes for:
2024-01-22 17:32 gotip-darwin-amd64_13 go@b16a1e3a runtime/pprof.TestVMInfo (log)
|
Change https://go.dev/cl/560935 mentions this issue: |
Found new dashboard test flakes for:
2024-01-30 18:58 gotip-darwin-amd64_13 go@0b1b6c15 runtime/pprof.TestVMInfo (log)
2024-01-30 23:37 gotip-darwin-amd64_12 go@ae457e81 runtime/pprof.TestVMInfo (log)
2024-01-30 23:37 gotip-darwin-amd64_14 go@ae457e81 runtime/pprof.TestVMInfo (log)
2024-01-31 14:20 gotip-darwin-amd64-nocgo go@13766fe7 runtime/pprof.TestVMInfo (log)
2024-01-31 16:50 gotip-darwin-amd64_13 go@1bb947b2 runtime/pprof.TestVMInfo (log)
2024-01-31 19:56 gotip-darwin-amd64_12 go@79738217 runtime/pprof.TestVMInfo (log)
2024-01-31 20:51 gotip-darwin-amd64_12 go@5c0d0929 runtime/pprof.TestVMInfo (log)
2024-01-31 20:51 gotip-darwin-amd64_13 go@5c0d0929 runtime/pprof.TestVMInfo (log)
2024-01-31 23:21 gotip-darwin-amd64_12 go@2f6a25f4 runtime/pprof.TestVMInfo (log)
2024-01-31 23:21 gotip-darwin-amd64_14 go@2f6a25f4 runtime/pprof.TestVMInfo (log)
2024-02-01 15:34 gotip-darwin-amd64_13 go@5b6cd3d0 runtime/pprof.TestVMInfo (log)
2024-02-01 18:09 gotip-darwin-amd64_12 go@18840865 runtime/pprof.TestVMInfo (log)
2024-02-01 19:29 gotip-darwin-amd64_13 go@29746b48 runtime/pprof.TestVMInfo (log)
2024-02-01 20:09 gotip-darwin-amd64_12 go@d864eac2 runtime/pprof.TestVMInfo (log)
2024-02-01 21:02 gotip-darwin-amd64_12 go@829f2ce3 runtime/pprof.TestVMInfo (log)
2024-02-01 21:42 gotip-darwin-amd64_13 go@c9d88ea2 runtime/pprof.TestVMInfo (log)
2024-02-01 21:42 gotip-darwin-amd64_14 go@c9d88ea2 runtime/pprof.TestVMInfo (log)
2024-02-01 22:47 gotip-darwin-amd64_13 go@ac08c05d runtime/pprof.TestVMInfo (log)
2024-02-01 22:57 gotip-darwin-amd64-nocgo go@6d3c1ce8 runtime/pprof.TestVMInfo (log)
2024-02-01 22:57 gotip-darwin-amd64_13 go@6d3c1ce8 runtime/pprof.TestVMInfo (log)
2024-02-01 22:59 gotip-darwin-amd64-nocgo go@117164f9 runtime/pprof.TestVMInfo (log)
2024-02-01 22:59 gotip-darwin-amd64_12 go@117164f9 runtime/pprof.TestVMInfo (log)
2024-02-02 15:13 gotip-darwin-amd64_12 go@244ccf47 runtime/pprof.TestVMInfo (log)
2024-02-02 15:22 gotip-darwin-amd64_13 go@149db960 runtime/pprof.TestVMInfo (log)
2024-02-02 17:06 gotip-darwin-amd64_12 go@3b83560b runtime/pprof.TestVMInfo (log)
2024-02-02 18:35 gotip-darwin-amd64_12 go@3d20a327 runtime/pprof.TestVMInfo (log)
2024-02-02 22:08 gotip-darwin-amd64_12 go@9819d826 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-05 14:52 gotip-darwin-amd64-nocgo go@e8d87728 runtime/pprof.TestVMInfo (log)
2024-02-05 14:52 gotip-darwin-amd64_12 go@e8d87728 runtime/pprof.TestVMInfo (log)
2024-02-05 15:30 gotip-darwin-amd64-nocgo go@76ff0caa runtime/pprof.TestVMInfo (log)
2024-02-05 15:30 gotip-darwin-amd64_12 go@76ff0caa runtime/pprof.TestVMInfo (log)
2024-02-05 20:59 gotip-darwin-amd64-nocgo go@6076edc5 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-06 12:43 gotip-darwin-amd64_14 go@6f44cc88 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-02 16:17 go1.22-darwin-amd64_14 release-branch.go1.22@b0957cfc runtime/pprof.TestVMInfo (log)
|
The previous attempt to fix this flake was incorrect in that it examined the vmmap output rather than the detailed error output for the 'resource shortage' message that triggers the retry, and hence failed to retry. This PR looks at the detailed error output. Fixes golang#62352 Change-Id: I4218b187528a95842556dc1ea27947ffcbfbc497 Reviewed-on: https://go-review.googlesource.com/c/go/+/558575 Auto-Submit: Michael Pratt <mpratt@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Michael Pratt <mpratt@google.com>
Found new dashboard test flakes for:
2024-02-19 08:55 gotip-darwin-amd64_12 go@5c92f43c runtime/pprof.TestVMInfo (log)
2024-02-19 15:44 gotip-darwin-amd64-nocgo go@cf52e709 runtime/pprof.TestVMInfo (log)
2024-02-19 15:44 gotip-darwin-amd64_13 go@cf52e709 runtime/pprof.TestVMInfo (log)
2024-02-19 20:29 gotip-darwin-amd64_14 go@7ecef2e3 runtime/pprof.TestVMInfo (log)
2024-02-19 20:44 gotip-darwin-amd64_12 go@0882ca7a runtime/pprof.TestVMInfo (log)
2024-02-19 20:51 gotip-darwin-amd64-nocgo go@aaf8e844 runtime/pprof.TestVMInfo (log)
2024-02-20 06:04 gotip-darwin-amd64_14 go@d42cd452 runtime/pprof.TestVMInfo (log)
2024-02-20 14:56 gotip-darwin-amd64_12 go@098a87fb runtime/pprof.TestVMInfo (log)
2024-02-20 14:56 gotip-darwin-amd64_13 go@0a046418 runtime/pprof.TestVMInfo (log)
2024-02-20 14:59 gotip-darwin-amd64_12 go@a3c35430 runtime/pprof.TestVMInfo (log)
2024-02-20 14:59 gotip-darwin-amd64_12 go@ff0b46cf runtime/pprof.TestVMInfo (log)
2024-02-20 16:10 gotip-darwin-amd64_13 go@ff4e45fb runtime/pprof.TestVMInfo (log)
2024-02-20 17:18 gotip-darwin-amd64_13 go@02785362 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-20 21:02 gotip-darwin-amd64_14 go@de65aa41 runtime/pprof.TestVMInfo (log)
2024-02-20 22:29 gotip-darwin-amd64-longtest go@5428cc4f runtime/pprof.TestVMInfo (log)
2024-02-20 22:29 gotip-darwin-amd64_12 go@5428cc4f runtime/pprof.TestVMInfo (log)
2024-02-20 22:29 gotip-darwin-amd64_13 go@5428cc4f runtime/pprof.TestVMInfo (log)
2024-02-20 22:40 gotip-darwin-amd64_14 go@29083529 runtime/pprof.TestVMInfo (log)
2024-02-20 22:55 gotip-darwin-amd64_12 go@1a8ee033 runtime/pprof.TestVMInfo (log)
2024-02-20 22:55 gotip-darwin-amd64_13 go@1a8ee033 runtime/pprof.TestVMInfo (log)
2024-02-21 00:55 gotip-darwin-amd64_12 go@d4112310 runtime/pprof.TestVMInfo (log)
2024-02-21 17:12 gotip-darwin-amd64_12 go@6c979d25 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-21 17:07 gotip-darwin-amd64_13 go@81609c45 runtime/pprof.TestVMInfo (log)
2024-02-21 18:47 gotip-darwin-amd64_13 go@c07b9b00 runtime/pprof.TestVMInfo (log)
2024-02-21 19:25 gotip-darwin-amd64_12 go@806aeb1e runtime/pprof.TestVMInfo (log)
2024-02-21 20:35 gotip-darwin-amd64_12 go@b27d02c0 runtime/pprof.TestVMInfo (log)
2024-02-21 20:35 gotip-darwin-amd64_13 go@b27d02c0 runtime/pprof.TestVMInfo (log)
2024-02-21 21:26 gotip-darwin-amd64_13 go@ccb6077d runtime/pprof.TestVMInfo (log)
2024-02-21 21:27 gotip-darwin-amd64_12 go@cdf3249d runtime/pprof.TestVMInfo (log)
2024-02-21 21:28 gotip-darwin-amd64_11 go@05c05796 runtime/pprof.TestVMInfo (log)
2024-02-22 05:31 gotip-darwin-amd64_12 go@7fd62ba8 runtime/pprof.TestVMInfo (log)
2024-02-22 15:37 gotip-darwin-amd64-nocgo go@638b9023 runtime/pprof.TestVMInfo (log)
2024-02-22 15:37 gotip-darwin-amd64_12 go@638b9023 runtime/pprof.TestVMInfo (log)
2024-02-22 16:40 gotip-darwin-amd64_13 go@f278f756 runtime/pprof.TestVMInfo (log)
2024-02-22 19:32 gotip-darwin-amd64_12 go@db57e5a0 runtime/pprof.TestVMInfo (log)
2024-02-22 19:32 gotip-darwin-amd64_13 go@db57e5a0 runtime/pprof.TestVMInfo (log)
2024-02-22 22:21 gotip-darwin-amd64_13 go@d892cb49 runtime/pprof.TestVMInfo (log)
2024-02-23 00:19 gotip-darwin-amd64-longtest go@d9be6097 runtime/pprof.TestVMInfo (log)
2024-02-23 05:06 gotip-darwin-amd64_13 go@faf2a841 runtime/pprof.TestVMInfo (log)
2024-02-23 05:09 gotip-darwin-amd64_12 go@27e104ba runtime/pprof.TestVMInfo (log)
2024-02-23 05:09 gotip-darwin-amd64_14 go@27e104ba runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-27 16:22 darwin-amd64-12_0 go@856355a9 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-23 18:08 gotip-darwin-amd64-longtest go@0e7c9846 runtime/pprof.TestVMInfo (log)
2024-02-23 18:29 gotip-darwin-amd64_13 go@c4e4afc9 runtime/pprof.TestVMInfo (log)
2024-02-23 18:31 gotip-darwin-amd64_12 go@e58486e5 runtime/pprof.TestVMInfo (log)
2024-02-24 00:04 gotip-darwin-amd64_12 go@ef84d62c runtime/pprof.TestVMInfo (log)
2024-02-24 00:04 gotip-darwin-amd64_13 go@ef84d62c runtime/pprof.TestVMInfo (log)
2024-02-26 20:45 gotip-darwin-amd64_12 go@08029be9 runtime/pprof.TestVMInfo (log)
2024-02-26 20:46 gotip-darwin-amd64_13 go@4760b333 runtime/pprof.TestVMInfo (log)
2024-02-26 20:46 gotip-darwin-amd64_12 go@f63faf36 runtime/pprof.TestVMInfo (log)
2024-02-26 20:48 gotip-darwin-amd64_13 go@519a7bb1 runtime/pprof.TestVMInfo (log)
2024-02-26 20:50 gotip-darwin-amd64_13 go@65172c20 runtime/pprof.TestVMInfo (log)
2024-02-26 20:57 gotip-darwin-amd64_12 go@601eb78d runtime/pprof.TestVMInfo (log)
2024-02-26 21:34 gotip-darwin-amd64_12 go@74642ddf runtime/pprof.TestVMInfo (log)
2024-02-27 16:21 gotip-darwin-amd64_12 go@f326b3e2 runtime/pprof.TestVMInfo (log)
2024-02-27 17:26 gotip-darwin-amd64_12 go@05845747 runtime/pprof.TestVMInfo (log)
2024-02-27 18:16 gotip-darwin-amd64_12 go@347ad523 runtime/pprof.TestVMInfo (log)
2024-02-27 19:24 gotip-darwin-amd64_12 go@a6a5c30d runtime/pprof.TestVMInfo (log)
2024-02-27 20:11 gotip-darwin-amd64_12 go@234390e7 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-27 21:07 gotip-darwin-amd64_13 go@b847d4cd runtime/pprof.TestVMInfo (log)
2024-02-27 21:18 go1.22-darwin-amd64_13 release-branch.go1.22@686662f3 runtime/pprof.TestVMInfo (log)
2024-02-27 21:22 go1.22-darwin-amd64_13 release-branch.go1.22@8fe2ad64 runtime/pprof.TestVMInfo (log)
2024-02-28 16:29 gotip-darwin-amd64_13 go@f8654408 runtime/pprof.TestVMInfo (log)
2024-02-28 16:44 gotip-darwin-amd64_13 go@b5a99eaa runtime/pprof.TestVMInfo (log)
2024-02-28 16:44 gotip-darwin-amd64_13 go@58911599 runtime/pprof.TestVMInfo (log)
2024-02-28 16:44 gotip-darwin-amd64_13 go@d1e8dc25 runtime/pprof.TestVMInfo (log)
2024-02-28 16:44 gotip-darwin-amd64_13 go@1df6db8e runtime/pprof.TestVMInfo (log)
2024-02-28 19:10 go1.22-darwin-amd64_13 release-branch.go1.22@5330cd22 runtime/pprof.TestVMInfo (log)
2024-02-28 20:32 gotip-darwin-amd64_13 go@a414fd79 runtime/pprof.TestVMInfo (log)
2024-02-28 20:35 gotip-darwin-amd64_13 go@a05ea985 runtime/pprof.TestVMInfo (log)
2024-02-28 22:57 gotip-darwin-amd64_13 go@288615dd runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-28 16:43 gotip-darwin-amd64_13 go@09bfea95 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-29 21:29 gotip-darwin-amd64_13 go@e9304133 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-03-04 17:34 gotip-darwin-amd64_13 go@4c08c125 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-03-04 17:30 gotip-darwin-amd64_13 go@ff35c382 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-03-04 17:26 gotip-darwin-amd64_13 go@dff3a00c runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-02-28 19:53 go1.22-darwin-amd64_13 release-branch.go1.22@056b0edc runtime/pprof.TestVMInfo (log)
|
Hi Bryan, I see that this is persisting. Is it a problem with the CI runners or should I disable this test? Cheers, Cos. |
Found new dashboard test flakes for:
2024-03-19 11:31 darwin-amd64-nocgo go@d14cf8f9 runtime/pprof.TestVMInfo (log)
|
@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... |
Found new dashboard test flakes for:
2024-03-21 00:10 gotip-darwin-amd64_12 go@7d4d71e5 runtime/pprof.TestVMInfo (log)
2024-03-21 00:52 gotip-darwin-amd64-longtest go@36cd8808 runtime/pprof.TestVMInfo (log)
2024-03-21 00:52 gotip-darwin-amd64_14 go@36cd8808 runtime/pprof.TestVMInfo (log)
2024-03-21 09:16 gotip-darwin-amd64_14 go@dc0527ee runtime/pprof.TestVMInfo (log)
2024-03-21 09:27 gotip-darwin-amd64-nocgo go@0a0758af runtime/pprof.TestVMInfo (log)
2024-03-21 09:29 gotip-darwin-amd64-longtest go@f2685395 runtime/pprof.TestVMInfo (log)
2024-03-21 11:49 gotip-darwin-amd64-longtest go@68a508cd runtime/pprof.TestVMInfo (log)
2024-03-21 11:49 gotip-darwin-amd64-nocgo go@cff7267e runtime/pprof.TestVMInfo (log)
2024-03-21 16:12 gotip-darwin-amd64_12 go@d9f97467 runtime/pprof.TestVMInfo (log)
2024-03-21 16:12 gotip-darwin-amd64_14 go@d9f97467 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-04-02 21:51 darwin-amd64-nocgo go@d08a9572 runtime/pprof.TestVMInfo (log)
|
Change https://go.dev/cl/579295 mentions this issue: |
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>
Found new dashboard test flakes for:
2024-03-21 17:29 go1.22-darwin-amd64-nocgo release-branch.go1.22@35b1a146 runtime/pprof.TestVMInfo (log)
2024-04-18 15:41 gotip-darwin-amd64_14 go@a973b425 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-04-19 16:55 gotip-darwin-amd64_12 go@f0d6ddfa runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-04-19 17:39 gotip-darwin-amd64_14 go@c260de24 runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-04-22 13:29 gotip-darwin-amd64-longtest go@2dddc7ef runtime/pprof.TestVMInfo (log)
|
Found new dashboard test flakes for:
2024-04-22 14:55 gotip-darwin-amd64_14 go@69aa1974 runtime/pprof.TestVMInfo (log)
|
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: