runtime: skip mayMoreStackMove in goroutine leak tests

mayMoreStackMove may introduce more scheduler chaos because of all the
stack movement (not as much as mayMoreStackPreempt) so let's disable the
tests here too, since we have evidence that they can produce false
negatives under this configuration. Though we're not 100% sure why this
is happening yet, let's at least stop the flow of flaky failures.

For #75729.

Change-Id: I16d13dba9a61fbd47563b21cbf188e4754f58213
Reviewed-on: https://go-review.googlesource.com/c/go/+/726526
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Michael Pratt <mpratt@google.com>

diff --git a/src/runtime/goroutineleakprofile_test.go b/src/runtime/goroutineleakprofile_test.go
index a0446b36f0471e045b0c2df863f00001171e3017..9ab92d17c4eb255188396770591d90faada8cf3d 100644 (file)
--- a/src/runtime/goroutineleakprofile_test.go
+++ b/src/runtime/goroutineleakprofile_test.go
@@ -14,10 +14,13 @@ import (
 )
 
 func TestGoroutineLeakProfile(t *testing.T) {
-       if strings.Contains(os.Getenv("GOFLAGS"), "mayMoreStackPreempt") {
-               // Some tests have false negatives under mayMoreStackPreempt. This may be a test-only issue,
-               // but needs more investigation.
-               testenv.SkipFlaky(t, 75729)
+       // Some tests have false negatives under mayMoreStackPreempt and mayMoreStackMove.
+       // This may be a test-only issue in that they're just sensitive to scheduling, but it
+       // needs more investigation.
+       for _, cfg := range []string{"mayMoreStackPreempt", "mayMoreStackMove"} {
+               if strings.Contains(os.Getenv("GOFLAGS"), cfg) {
+                       testenv.SkipFlaky(t, 75729)
+               }
        }
 
        // Goroutine leak test case.