+1 maintenance report

[Seth Arnold]

On Fri, Feb 12, 2021 at 06:10:32PM -0800, Bryce Harrington wrote:
> This next set had test failures due to intermittent network issues, or
> other 'flaky' troubles, and passed on a simple retrigger.  (I'm not

Could we build a retriggerbot that smashes the retry button three times
before bothering any humans about failed tests?

Hitting retry is often the first troubleshooting step people take; I've
heard tests may be retried something like ten times by different people,
each of whom was taking a reasonable enough "first debugging step"
without noticing that other people have also done the same.

This way, any failures that bubble up to a human would be 'bad enough'
that it requires a human to address. (Of course, this may require tuning
the 'three' in my suggestion based on how many retries are usually
necessary.) Whoever is looking at an error could skip a retry at that
point and start right away looking at the test in question.

Thanks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20210213/fcd9207f/attachment.sig>