Frequently our CI tests break with messages like
running 4 tests
test validator::find_wrappers::tests::should_handle_no_wrappers_found ... ok
test validator::find_wrappers::tests::should_locate_gradle_wrappers ... ok
test validator::tests::should_validate_local_project_when_checksum_matches ... FAILED
test validator::tests::should_validate_local_project_when_checksum_does_not_match ... ok
failures:
---- validator::tests::should_validate_local_project_when_checksum_matches stdout ----
thread 'validator::tests::should_validate_local_project_when_checksum_matches' (2968) panicked at src/validator/fetch_checksums.rs:14:62:
Cannot fetch checksums: reqwest::Error { kind: Request, url: "https://cdn.statically.io/gh/gradle/actions/main/sources/src/wrapper-validation/wrapper-checksums.json", source: TimedOut }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
So far, we've been relying on statically.io as an easy way to expose Github assets through a CDN, eventually avoiding issues like Github rate-limits along the way. However, we should consider exposing Gradle checksums through a CDN we can control like Cloudflare or Fastly.
Frequently our CI tests break with messages like
So far, we've been relying on statically.io as an easy way to expose Github assets through a CDN, eventually avoiding issues like Github rate-limits along the way. However, we should consider exposing Gradle checksums through a CDN we can control like Cloudflare or Fastly.