[ARROW-1583] Use "travis_retry" function in some key places to reduce CI flakiness

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• External issue URL: https://github.com/apache/arrow/issues/17596
• Assignee: Unassigned
• Reporter: Wes McKinney
• Created: 20/Sep/17 18:06
• Updated: 11/Jan/23 07:15
• Resolved: 10/Nov/18 21:39

Description

There's enough things that can go wrong in our CI due to external package registries that we can often end up with spurious failures not caused by code changes.

For example, here is an NPM registry failure:

https://travis-ci.org/apache/arrow/jobs/277798491#L941

I have seen Maven Central fail or anaconda.org fail in the past, too. Some of these package commands that hit external resources could be wrapped in travis_retry to give them another shot at success