greplogs --dashboard -md -l -e \(\?ms\)runtime\\.throw.\*FAIL\\s+compress/flate

2021-10-07T14:01:52-ecb2f23/android-386-emu
2021-10-06T21:06:48-197b328/darwin-arm64-11_0-toothrot
2021-10-06T19:45:35-e38ec96/darwin-arm64-11_0-toothrot
2021-10-06T13:47:50-810b08b/darwin-arm64-11_0-toothrot
2021-10-05T21:25:51-6ae3afa/darwin-arm64-11_0-toothrot
2021-10-05T20:35:41-75773b0/android-arm64-corellium
2021-10-05T20:35:41-75773b0/darwin-arm64-11_0-toothrot
2021-10-05T19:28:36-7ae83c8/darwin-arm64-11_0-toothrot
2021-02-19T00:41:36-40765ff/netbsd-amd64-9_0
2020-12-05T12:36:42-be9379f/plan9-arm
2020-12-02T14:20:12-0433845/plan9-arm
2020-11-28T18:42:44-4ce0a7c/plan9-arm
2020-11-24T19:53:18-65dcd15/plan9-arm
2020-11-11T20:48:31-4c174a7/plan9-arm

I'm inclined to chalk the plan9-arm and failures up to platform-specific bugs, and the netbsd failure looks like #44269. But I have no explanation for the darwin-arm64 and android-*-emu failures starting October 5 — that looks like a separate regression to me.

@jeremyfaller, can you suggest someone to route this to?