hash/maphash: TestSmhasher* failures on 386

[gopherbot]

#!watchflakes
default <- pkg == "hash/maphash" && test ~ `TestSmhasher.*` && goarch == "386"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestSmhasherPermutation
=== PAUSE TestSmhasherPermutation
=== CONT  TestSmhasherPermutation

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "hash/maphash" && test == "TestSmhasherPermutation"

2024-02-20 14:56 gotip-linux-386-longtest go@0a046418 hash/maphash.TestSmhasherPermutation [ABORT] (log)

=== RUN   TestSmhasherPermutation
=== PAUSE TestSmhasherPermutation
=== CONT  TestSmhasherPermutation

2024-02-20 14:59 gotip-linux-386-longtest go@ff0b46cf hash/maphash.TestSmhasherPermutation [ABORT] (log)

=== RUN   TestSmhasherPermutation
=== PAUSE TestSmhasherPermutation
=== CONT  TestSmhasherPermutation

— watchflakes

[prattmic]

This seems to be specific to 386, and general to all TestSmhasher tests. Adjusting the matcher.

[prattmic]

The first failure was on https://go.dev/cl/564576, which seems like a likely cause.

Note that the runtime equivalent of these tests is skipped on 32-bit systems after #43130. But the symptom is different. That one had hash collisions, this one has no log output at all. My best guess is that it is OOM-killed.

cc @qiulaidongfeng @randall77

[gopherbot]

Change https://go.dev/cl/565536 mentions this issue: Revert "hash/maphash: parallel run test"

[gopherbot]

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

#!watchflakes
default <- pkg == "hash/maphash" && test ~ "TestSmhasher.*" && goos == "386"

And the problems were:

script:2.44: ~ requires backquoted regexp

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

— watchflakes