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

["Rok Mihevc (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rok Mihevc updated ARROW-1583:
------------------------------
    External issue URL: https://github.com/apache/arrow/issues/17596

> Use "travis_retry" function in some key places to reduce CI flakiness
> ---------------------------------------------------------------------
>
>                 Key: ARROW-1583
>                 URL: https://issues.apache.org/jira/browse/ARROW-1583
>             Project: Apache Arrow
>          Issue Type: Improvement
>            Reporter: Wes McKinney
>            Priority: Major
>
> 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



--
This message was sent by Atlassian Jira
(v8.20.10#820010)