Skip to content

some useful texttree helpers from baboon #1462

some useful texttree helpers from baboon

some useful texttree helpers from baboon #1462

Triggered via push December 30, 2024 18:47
Status Failure
Total duration 13m 32s
Artifacts

build.yml

on: push
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

10 errors and 41 warnings
build-jvm (17, 2.12)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
build-jvm (11, 2.13)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
build-jvm (11, 3)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
build-jvm (11, 2.12)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
build-jvm (17, 3)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
build-jvm (22, 2.13)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
build-jvm (17, 2.13)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
build-jvm (22, 2.12)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
build-jvm (22, 3)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
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
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 (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 (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.13)
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)
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, 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)
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-jvm (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-jvm (17, 2.12)
Test report summary exceeded limit of 65535 bytes and will be trimmed
build-jvm (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.13)
Test report summary exceeded limit of 65535 bytes and will be trimmed
build-jvm (11, 3)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build-jvm (11, 3)
Codecov: Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
build-jvm (11, 3)
Test report summary exceeded limit of 65535 bytes and will be trimmed
build-jvm (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-jvm (11, 2.12)
Test report summary exceeded limit of 65535 bytes and will be trimmed
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)
Codecov: Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
build-jvm (17, 3)
Test report summary exceeded limit of 65535 bytes and will be trimmed
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)
Test report summary exceeded limit of 65535 bytes and will be trimmed
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)
Test report summary exceeded limit of 65535 bytes and will be trimmed
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)
Test report summary exceeded limit of 65535 bytes and will be trimmed
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)
Codecov: Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
build-jvm (22, 3)
Test report summary exceeded limit of 65535 bytes and will be trimmed