jepsen: ignore some install errors

[andreimatei]

Two failures. Seem to have been transient.

| Could not transfer artifact org.clojure:clojure:jar:1.9.0 from/to central (https://repo1.maven.org/maven2/): GET request of: org/clojure/clojure/1.9.0/clojure-1.9.0.jar from central failed
| Could not find artifact org.clojure:clojure:jar:1.9.0 in clojars (https://repo.clojars.org/)
| This could be due to a typo in :dependencies, file system permissions, or network issues.
| If you are behind a proxy, try setting the 'http_proxy' environment variable.

| Failed to read artifact descriptor for commons-codec:commons-codec:jar:1.6
| This could be due to a typo in :dependencies, file system permissions, or network issues.

Fixes #56695
Fixes #56645

Release note: None

[cockroach-teamcity]

This change is 

[knz]

No objection for me - but I would like to highlight this is one more test that is too happy to go and fetch dependencies externally. Why don't we have our own local copies of these files?

cc @jlinder - what would be the better fix here?

[tbg]

LGTM

Andrei has long been beating the drum about making these self-contained, but we haven't had the resources to do it. Once we build abstractions here, they need to be maintained, and so unless dev-inf can take this on I think we'll just have to live with the status quo.

[jlinder]

Dev-inf hasn't had time to focus on roachtest since before July and won't until next year sometime.

cc @jlinder - what would be the better fix here?

The most obvious fix that doesn't download the file from the source location on every run is:

1. create a google storage bucket
2. place the files we need there
3. download the files from the bucket
4. add some tracking mechanism to check for new versions of the files periodically (assuming they get updated) and automatically download the new file and place it in the bucket

If there are files loaded by the runs in AWS, add this to the above:

1. create an S3 bucket
2. place the files in it that are used by the tests run in S3
3. add a mechanism to roachtest that downloads the target files from the S3 bucket / gs bucket according to whether it's running in GCP or AWS
4. check for new versions of the files with the above defined tracking mechanism + placing the new versions in the S3 bucket

[jlinder]

Why don't we have our own local copies of these files?

Added an issue to track this feature request. #56856

[nvanbenschoten]

We'll want to backport this as well, as we've also seen this failure on other release branches: https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+%22If+you+are+behind+a+proxy%2C+try+setting+the+%27http_proxy%27+environment+variable.%22.

[andreimatei]

bors r+

[craig]

Build succeeded:

• GitHub CI (Cockroach)