Cataloguing spurious failures in CI

[chreekat]

What initially got me involved in this project was a discussion with @fruffy about handling spurious failures in CI. This is a topic that's probably bigger than one Issue, but I wanted to at least break open that initial discussion and start understanding the scope of the problem better.

As a starting point, I went and looked at recent failures in GitHub Actions. I quickly found this failure to download a tarball, which seems like a clear example of something that shouldn't result in a failed CI run. (I was able to download it just fine when I tried right now.)

Surely there are others. What would be very helpful is if regular contributors could give me other examples!

If people could just add a comment on this issue whenever they see something similar, that would be a nice starting point.

[fruffy]

One package that fails fairly frequently is the ones we host on opensuse.org, e.g. #5054

The fix for this is likely the same fix as building out our own debian release infrastructure: #4738