[GitHub] [metron] nickwallen opened a new pull request #1433: METRON-2143 Travis Build Fails to Download Maven

[GitBox <gi...@apache.org>]

nickwallen opened a new pull request #1433: METRON-2143 Travis Build Fails to Download Maven
URL: https://github.com/apache/metron/pull/1433
 
 
   This is a transient error that occurs occasionally when the Apache Mirrors are temporarily unavailable and the build is unable to download Maven.
   ```
   0.50s$ wget https://archive.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.zip
   --2019-05-22 21:24:16--  https://archive.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.zip
   Resolving archive.apache.org (archive.apache.org)... 163.172.17.199
   Connecting to archive.apache.org (archive.apache.org)|163.172.17.199|:443... connected.
   HTTP request sent, awaiting response... 503 Service Unavailable
   2019-05-22 21:24:17 ERROR 503: Service Unavailable.
   The command "wget https://archive.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.zip" failed and exited with 8 during .
   ```
   
   The `wget` tool will retry many types of failures by default during a download, but will not retry some errors like a 503. After reading the man page, it seems that the following option is exactly what we need to retry a 503 and hopefully avoid this issue.
   ```
   --retry-connrefused
   Consider "connection refused" a transient error and try again.  Normally Wget gives up on a URL when it is unable to connect to the site because failure to connect is taken as a sign that the server is not running at all and that retries would not help.  This option is for mirroring unreliable sites whose servers tend to disappear for short periods of time.
   ```
   
   
   ## Pull Request Checklist
   
   - [ ] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
   - [ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
   - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
   
   
   ### For code changes:
   - [ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
   - [ ] Have you included steps or a guide to how the change may be verified and tested manually?
   - [ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
   - [ ] Have you written or updated unit tests and or integration tests to verify your changes?
   - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services