Skip to content

extractSelf convenience helper #1460

extractSelf convenience helper

extractSelf convenience helper #1460

Triggered via pull request December 23, 2024 20:12
Status Failure
Total duration 11m 16s
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

38 errors and 58 warnings
build-js (22, 2.12)
Process completed with exit code 1.
build-js (22, 2.12)
No test report files were found
build-js (22, 3)
No test report files were found
build-js (22, 3)
Process completed with exit code 1.
test-site (22, 2.13)
Process completed with exit code 1.
build-js (17, 3)
No test report files were found
build-js (17, 3)
Process completed with exit code 1.
build-js (17, 2.12)
Process completed with exit code 1.
build-js (17, 2.12)
No test report files were found
build-js (17, 2.13)
Process completed with exit code 1.
build-js (17, 2.13)
No test report files were found
build-js (11, 2.12)
Process completed with exit code 1.
build-js (11, 2.12)
No test report files were found
build-js (11, 2.13)
No test report files were found
build-js (11, 2.13)
Process completed with exit code 1.
build-js (11, 3)
No test report files were found
build-js (11, 3)
Process completed with exit code 1.
build-js (22, 2.13)
Process completed with exit code 1.
build-js (22, 2.13)
No test report files were found
build-jvm (11, 2.12)
Process completed with exit code 1.
build-jvm (11, 2.12)
No test report files were found
build-jvm (11, 2.13)
No test report files were found
build-jvm (11, 2.13)
Process completed with exit code 1.
build-jvm (22, 2.12)
No test report files were found
build-jvm (22, 2.12)
Process completed with exit code 1.
build-jvm (17, 2.12)
Process completed with exit code 1.
build-jvm (17, 2.12)
No test report files were found
build-jvm (22, 2.13)
Process completed with exit code 1.
build-jvm (22, 2.13)
No test report files were found
build-jvm (11, 3)
Process completed with exit code 1.
build-jvm (11, 3)
No test report files were found
build-jvm (22, 3)
Process completed with exit code 1.
build-jvm (22, 3)
No test report files were found
build-jvm (17, 3)
Process completed with exit code 1.
build-jvm (17, 3)
No test report files were found
build-jvm (17, 2.13)
No test report files were found
build-jvm (17, 2.13)
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 (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 (22, 2.12)
No file matches path **/target/test-reports/TEST-*.xml
build-js (22, 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, 3)
No file matches path **/target/test-reports/TEST-*.xml
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 (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 (17, 3)
No file matches path **/target/test-reports/TEST-*.xml
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.12)
No file matches path **/target/test-reports/TEST-*.xml
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, 2.13)
No file matches path **/target/test-reports/TEST-*.xml
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 (11, 2.12)
No file matches path **/target/test-reports/TEST-*.xml
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-js (11, 2.13)
No file matches path **/target/test-reports/TEST-*.xml
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 (11, 3)
No file matches path **/target/test-reports/TEST-*.xml
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 (22, 2.13)
No file matches path **/target/test-reports/TEST-*.xml
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.12)
No file matches path **/target/test-reports/TEST-*.xml
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, 2.13)
No file matches path **/target/test-reports/TEST-*.xml
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-jvm (22, 2.12)
No file matches path **/target/test-reports/TEST-*.xml
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 (17, 2.12)
No file matches path **/target/test-reports/TEST-*.xml
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.13)
No file matches path **/target/test-reports/TEST-*.xml
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 (11, 3)
No file matches path **/target/test-reports/TEST-*.xml
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, 3)
No file matches path **/target/test-reports/TEST-*.xml
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, 3)
No file matches path **/target/test-reports/TEST-*.xml
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.13)
No file matches path **/target/test-reports/TEST-*.xml