Skip to content
CI

feat: start testing on Bazel 8 #1134

Sign in to view logs

feat: start testing on Bazel 8

feat: start testing on Bazel 8 #1134

Triggered via pull request October 25, 2024 16:27
@alexeaglealexeagle
synchronize #407
revert-404-revert-401-alexeagle-patch-2
Status Failure
Total duration 3m 4s
Artifacts –

ci.yaml

on: pull_request
bazel-test  /  matrix-prep-os
0s
bazel-test / matrix-prep-os
bazel-test  /  matrix-prep-bazelversion
6s
bazel-test / matrix-prep-bazelversion
integration-test
2m 33s
integration-test
Matrix: bazel-test / test
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
bazel-test / test (ubuntu-latest, last_rc, example, false)
Process completed with exit code 1.
bazel-test / test (ubuntu-latest, last_rc, ., true)
Process completed with exit code 1.
bazel-test / test (ubuntu-latest, 8.0.0rc1, ., true)
Process completed with exit code 1.
bazel-test / test (ubuntu-latest, 8.0.0rc1, example, true)
Process completed with exit code 1.
bazel-test / test (ubuntu-latest, last_rc, example, true)
Process completed with exit code 1.
integration-test
Process completed with exit code 1.
bazel-test / test (ubuntu-latest, 8.0.0rc1, example, false)
Process completed with exit code 1.
integration-test
The following actions uses node12 which is deprecated and will be forced to run on node16: mig4/setup-bats@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
integration-test
The following actions use a deprecated Node.js version and will be forced to run on node20: mig4/setup-bats@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/