Update zio, zio-managed to 2.1.13 #1440
Triggered via pull request
November 21, 2024 13:51
Status
Failure
Total duration
22m 18s
Artifacts
–
build.yml
on: pull_request
checksecret
0s
Matrix: test-site
Matrix: build-js
Matrix: build-jvm
Annotations
2 errors and 45 warnings
test-site (22, 2.13)
Process completed with exit code 1.
|
all-good
Process completed with exit code 1.
|
build-js (11, 2.12)
Failed to restore: Cache service responded with 429
|
build-js (11, 2.12)
Failed to restore: Cache service responded with 429
|
build-js (11, 2.13)
Failed to restore: Cache service responded with 429
|
build-js (11, 2.13)
Failed to restore: Cache service responded with 429
|
build-js (17, 2.12)
Failed to restore: Cache service responded with 429
|
build-js (17, 2.12)
Failed to restore: Cache service responded with 429
|
build-js (17, 2.12)
Failed to restore: Cache service responded with 429
|
build-js (22, 2.12)
Failed to restore: Cache service responded with 429
|
build-js (11, 3)
Failed to restore: Cache service responded with 429
|
build-js (11, 3)
Failed to restore: Cache service responded with 429
|
build-js (11, 3)
Failed to restore: Cache service responded with 429
|
build-js (17, 3)
Failed to restore: Cache service responded with 429
|
build-js (17, 3)
Failed to restore: Cache service responded with 429
|
build-js (17, 3)
Failed to restore: Cache service responded with 429
|
build-js (22, 2.13)
Failed to restore: Cache service responded with 429
|
build-js (22, 2.13)
Failed to restore: Cache service responded with 429
|
build-js (22, 2.13)
Failed to restore: Cache service responded with 429
|
build-js (17, 2.13)
Failed to restore: Cache service responded with 429
|
build-js (17, 2.13)
Failed to restore: Cache service responded with 429
|
build-js (17, 2.13)
Failed to restore: Cache service responded with 429
|
build-js (22, 3)
Failed to restore: Cache service responded with 429
|
build-js (22, 3)
Failed to restore: Cache service responded with 429
|
build-js (22, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (11, 2.12)
Failed to restore: Cache service responded with 429
|
build-jvm (11, 2.12)
Failed to restore: Cache service responded with 429
|
build-jvm (11, 2.12)
Failed to restore: Cache service responded with 429
|
build-jvm (11, 2.13)
Failed to restore: Cache service responded with 429
|
build-jvm (11, 2.13)
Failed to restore: Cache service responded with 429
|
build-jvm (11, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (11, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (11, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (17, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (17, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (17, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (17, 2.12)
Failed to restore: Cache service responded with 429
|
build-jvm (17, 2.12)
Failed to restore: Cache service responded with 429
|
build-jvm (17, 2.12)
Failed to restore: Cache service responded with 429
|
build-jvm (22, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (22, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (22, 3)
Failed to restore: Cache service responded with 429
|
build-jvm (22, 2.13)
Failed to restore: Cache service responded with 429
|
build-jvm (22, 2.13)
Failed to restore: Cache service responded with 429
|
build-jvm (22, 2.12)
Failed to restore: Cache service responded with 429
|
build-jvm (22, 2.12)
Failed to restore: Cache service responded with 429
|
build-jvm (22, 2.12)
Failed to restore: Cache service responded with 429
|