Skip to content

Update sbt-pgp to 2.3.1 #1453

Update sbt-pgp to 2.3.1

Update sbt-pgp to 2.3.1 #1453

Triggered via pull request December 11, 2024 14:06
Status Failure
Total duration 5m 26s
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

20 errors and 40 warnings
build-js (11, 3)
Process completed with exit code 1.
build-js (17, 2.12)
Process completed with exit code 1.
build-js (17, 2.13)
Process completed with exit code 1.
build-js (17, 3)
Process completed with exit code 1.
build-js (22, 2.13)
Process completed with exit code 1.
test-site (22, 2.13)
Process completed with exit code 1.
build-js (11, 2.12)
Process completed with exit code 1.
build-js (22, 2.12)
Process completed with exit code 1.
build-js (11, 2.13)
Process completed with exit code 1.
build-jvm (11, 2.12)
Process completed with exit code 1.
build-jvm (11, 2.13)
Process completed with exit code 1.
build-jvm (11, 3)
Process completed with exit code 1.
build-jvm (22, 3)
Process completed with exit code 1.
build-jvm (17, 3)
Process completed with exit code 1.
build-jvm (17, 2.13)
Process completed with exit code 1.
build-jvm (17, 2.12)
Process completed with exit code 1.
build-jvm (22, 2.13)
Process completed with exit code 1.
build-jvm (22, 2.12)
Process completed with exit code 1.
build-js (22, 3)
Process completed with exit code 1.
all-good
Process completed with exit code 1.
checksecret
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-js (11, 3)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-js (17, 2.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-js (17, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-js (17, 3)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-js (22, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-site (22, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-js (11, 2.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-js (22, 2.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-js (11, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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, 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 (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 (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.13)
Failed to restore: Cache service responded with 429
build-jvm (17, 2.13)
Failed to restore: Cache service responded with 429
build-jvm (17, 2.13)
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, 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.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
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