#!watchflakes
default <- `some test left a core file behind`

Issue created automatically to collect these failures.

Example (log):

PASS
runtime.test: some test left a core file behind
FAIL    runtime 394.801s

— watchflakes

Comment From: gopherbot

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime:mayMoreStackMove" && test == ""
2024-09-13 17:15 gotip-linux-amd64-longtest go@d79e6bec runtime:mayMoreStackMove (log) PASS runtime.test: some test left a core file behind FAIL runtime 394.801s

— watchflakes

Comment From: gopherbot

Sorry, but there were parse errors in the watch flakes script. The script I found was:

#!watchflakes
default <- "some test left a core file behind"

And the problems were:

script:2.12: unexpected quoted string some test left a core file behind

See https://go.dev/wiki/Watchflakes for details.

— watchflakes

Comment From: gopherbot

Found new dashboard test flakes for:

#!watchflakes
default <- `some test left a core file behind`
2025-01-07 20:50 go1.24-linux-arm64-longtest release-branch.go1.24@b50ccef6 runtime:mayMoreStackMove (log) PASS runtime.test: some test left a core file behind FAIL runtime 314.801s

— watchflakes

Comment From: gopherbot

Found new dashboard test flakes for:

#!watchflakes
default <- `some test left a core file behind`
2025-02-03 16:38 gotip-linux-amd64-goamd64v3 go@f7b8dd90 runtime (log) PASS runtime.test: some test left a core file behind FAIL runtime 44.821s

— watchflakes

Comment From: gopherbot

Found new dashboard test flakes for:

#!watchflakes
default <- `some test left a core file behind`
2025-03-10 21:20 gotip-linux-riscv64 go@574a9fa6 runtime (log) PASS runtime.test: some test left a core file behind FAIL runtime 125.473s

— watchflakes

Comment From: gopherbot

Found new dashboard test flakes for:

#!watchflakes
default <- `some test left a core file behind`
2025-03-13 12:16 gotip-linux-amd64-longtest-noswissmap go@d7f58834 runtime (log) PASS runtime.test: some test left a core file behind FAIL runtime 138.389s

— watchflakes

Comment From: gopherbot

Found new dashboard test flakes for:

#!watchflakes
default <- `some test left a core file behind`
2025-05-12 19:27 gotip-linux-amd64-newinliner go@18431a1c runtime (log) PASS runtime.test: some test left a core file behind FAIL runtime 55.647s

— watchflakes

Comment From: gopherbot

Found new dashboard test flakes for:

#!watchflakes
default <- `some test left a core file behind`
2025-06-16 17:05 gotip-linux-amd64-longtest go@ea00461b runtime:mayMoreStackMove (log) PASS runtime.test: some test left a core file behind FAIL runtime 434.477s
2025-06-16 17:05 gotip-linux-amd64-longtest go@ea00461b runtime:runtime:gccheckmark (log) PASS runtime.test: some test left a core file behind FAIL runtime 47.931s
2025-06-16 17:05 gotip-linux-amd64-longtest-noswissmap go@ea00461b runtime:mayMoreStackMove (log) PASS runtime.test: some test left a core file behind FAIL runtime 431.753s
2025-06-16 17:05 gotip-linux-amd64-longtest-noswissmap go@ea00461b runtime:runtime:gccheckmark (log) PASS runtime.test: some test left a core file behind FAIL runtime 44.934s

— watchflakes