test: failures in `maplinear.go` with `iterdelete: too slow` on linux-mips*-rtrk

[bcmills]

#!watchflakes
post <- pkg == "maplinear.go" && `iterdelete: too slow` && goarch ~ `mips`

##### ../test
# go run run.go -- maplinear.go
exit status 2
panic: iterdelete: too slow: 40000 inserts: 2.755283259s; 80000 inserts: 9.103015471s


goroutine 1 [running]:
panic({0xc7440, 0xc000010030})
	/tmp/gobuilder-mips64/go/src/runtime/panic.go:987 +0x4e0 fp=0xc00006ce88 sp=0xc00006cdd0 pc=0x50670
main.checkLinear({0xd8451, 0xa}, 0x9c4, 0xdfda8)
	/tmp/gobuilder-mips64/go/test/maplinear.go:59 +0x27c fp=0xc00006cf58 sp=0xc00006ce88 pc=0xb9dfc
main.main()
	/tmp/gobuilder-mips64/go/test/maplinear.go:158 +0x25c fp=0xc00006cf80 sp=0xc00006cf58 pc=0xbab4c
runtime.main()
	/tmp/gobuilder-mips64/go/src/runtime/proc.go:250 +0x308 fp=0xc00006cfd8 sp=0xc00006cf80 pc=0x54158
runtime.goexit()
	/tmp/gobuilder-mips64/go/src/runtime/asm_mips64x.s:617 +0x4 fp=0xc00006cfd8 sp=0xc00006cfd8 pc=0x88d7c

greplogs -l -e FAIL\\s+maplinear\\.go
2022-06-21T17:32:57-530511b/linux-mips64-rtrk
2020-02-21T20:59:36-bc5fc6d/linux-mips64-rtrk

Perhaps a good first step would be to double-check whether the test's timing expectations are reasonable for this builder?

(attn @golang/mips; CC @golang/runtime)

[bcmills]

Hmm — @bogojevic and @milanknezevic are listed as the maintainers for this builder, but apparently didn't accept the invite to @golang/mips (maybe it got spam-filtered by accident?).

[mengzhuo]

I've contact them, no response too.
CC @wzssyqa

[milanknezevic]

Hello @bcmills, @mengzhuo, sorry for late response. I'm not able to work on maintaining of mips builders because I do not have access to them any more.

[Fearyncess]

Hello @bcmills, @mengzhuo, sorry for late response. I'm not able to work on maintaining of mips builders because I do not have access to them any more.

@milanknezevic
are you the rtrk's builder provider? will the builders still be working in the future? if not, we (cip united) can provide some mips machines for replacement or add more powerful building machines.

[draganmladjenovic]

@Fearyncess @bcmills @bcmills I'm currently maintaining these machines in some capacity. They should be working for the foreseeable future, but it is always better to add stronger machines, given that we share the same host for 32-bit and 64-bit MIPS variants.

[bcmills]

@draganmladjenovic, could you send a change to update x/build/dashboard (and perhaps x/build/internal/gophers) with current contact information for the rtrk machines?

[bcmills]

Also mipsle (not just mips64).

greplogs -l -e FAIL\\s+maplinear\\.go --since=2022-06-22
2022-06-30T21:52:06-af725f4/linux-mipsle-rtrk

[gopherbot]

Change https://go.dev/cl/415715 mentions this issue: dashboard: update host-linux-mips64*-rtrk owner