Update: #296 doesn't seem to have done the trick. A few more possible approaches:

• Retry the entire job in order to give more time for the network issue to resolve itself
• Maybe part of the issue is that the connection is bad, and the retry is reusing the bad connection? Maybe we could implement our own manual retry logic?
• Maybe we could somehow cache the needed crates so the jobs usually don't have to re-download?

Old text

Over the past few weeks, most full CI runs (currently 149 jobs) have had at least one failure due to Cargo failing to download a package even after 3 retries (the default value for the net.retry configuration option). Hopefully increasing the number of retries will make this less common.

Note that this was previously encountered in #225. #289 made the errors more obvious, but didn't make them any less common.