Reduce impact of networking slowdowns #374
Conversation
|
@edsantiago PTAL when you have a moment, this isn't critical. |
|
Cirrus CI build successful. Found built image names and IDs:
|
I don't, this is purely speculative. I do recall on occasion, an entire repo. mirror (or single package) will flake irrecoverably. In those cases you just need to wait and try again later. Sometimes the next day.
That's my recollection as well, and yes I probably should increase that timeout as well. |
Previously if a repository server, the internet, or the execution environment experienced some kind of networking slowdown, it could lead to a package install or update timeout failure. Increase resiliency in these situations with additional retries, timeouts, and lowered minimum rates. Also increase the timeout on the related Cirrus-CI tasks. Signed-off-by: Chris Evich <cevich@redhat.com>
cevich
force-pushed
the
rm_network_flakes
branch
from
77f48bd to
0a1e3db
Compare
|
force-push: Add/increase timeouts for the Cirrus-CI tasks. @edsantiago In case it's not clear, the primary target is the nested-virt Fedora base image builds. But I'm not married to this PR, it's really just speculation on increasing build-problem/flake resiliency. If you feel it's unnecessary, adds too much complexity, or whatever I'll just close it w/o any hard feelings. |
|
Cirrus CI build successful. Found built image names and IDs:
|
|
Identical to #375 (comment) |
Previously if a repository server, the internet, or the execution
environment experienced some kind of networking slowdown, it could lead
to a package install or update timeout failure. Increase resiliency in
these situations with additional retries, timeouts, and lowered minimum
rates. Also increase the timeout on the related Cirrus-CI tasks.