Skip to content

Update zio, zio-managed to 2.1.13 #1440

Update zio, zio-managed to 2.1.13

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
checksecret
Matrix: test-site
Matrix: build-js
Matrix: build-jvm
Matrix: publish-artifacts
Matrix: publish-site
all-good
2s
all-good
Fit to window
Zoom out
Zoom in

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