x/build: bot netbsd-arm-bsiegert--rpi3 reported as broken

[gopherbot]

The bot netbsd-arm-bsiegert--rpi3 has been reported as broken. It is currently in "dead" state. Please work to resolve the issue.

@golang/netbsd
@golang/arm

— watchflakes

[cagedmantis]

@bsiegert

[bsiegert]

The bot has been pretty unstable as of late, I have been rebooting it when it hangs. That said, this is the first time that gopherbot filed an issue. Is this a new functionality?

FWIW, the machine is rebooted and working again.

[cagedmantis]

@bsiegert Yes, we are trying out a new automated broken bot detection system. Any feedback provided on the system would be appreciated.

[bsiegert]

@cagedmantis It would be nice if I could opt out of these for the netbsd-arm builders specifically. Both machines are pretty unstable at the moment. I have separate monitoring alerting me that they need to be rebooted, so these are a bit redundant.

In general, the idea is good though!

[cagedmantis]

@bsiegert Thanks for the feedback. I think the current scanning algorithm is a bit sensitive. I plan on changing it so that if a machine is in a bad state for 24 hours (or some other sane amount of time) then it will create an issue. That would probably reduce the noise for unstable bots. Does that sound like a good compromise? We also want to exclude bots that have a known issue from having issues created for them. Would that suffice or would you still rather have them excluded for now?