Skip to content
Continuous Integration

Use a more consistent way of finding well-known protos for build scripts #561

Sign in to view logs

Use a more consistent way of finding well-known protos for build scripts

Use a more consistent way of finding well-known protos for build scripts #561

Triggered via push June 13, 2024 15:53
@ipetr0vipetr0v
pushed 536321e
main
Status Failure
Total duration 2h 0m 28s
Artifacts –

ci.yaml

on: push
Matrix: xtask
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 1 warning
xtask (run-bazel-tests)
Process completed with exit code 2.
xtask (run-cargo-clippy)
The job running on runner GitHub Actions 11 has exceeded the maximum execution time of 120 minutes.
xtask (run-cargo-clippy)
The operation was canceled.
xtask (completion)
The job running on runner GitHub Actions 2 has exceeded the maximum execution time of 120 minutes.
xtask (completion)
The operation was canceled.
xtask (run-cargo-deny)
The job running on runner GitHub Actions 20 has exceeded the maximum execution time of 120 minutes.
xtask (run-cargo-deny)
The operation was canceled.
xtask (run-cargo-fuzz -- -max_total_time=2)
The job running on runner GitHub Actions 7 has exceeded the maximum execution time of 120 minutes.
xtask (run-cargo-fuzz -- -max_total_time=2)
The operation was canceled.
xtask (run-cargo-udeps)
The job running on runner GitHub Actions 14 has exceeded the maximum execution time of 120 minutes.
xtask (run-cargo-udeps)
The operation was canceled.
xtask (check-format)
The job running on runner GitHub Actions 3 has exceeded the maximum execution time of 120 minutes.
xtask (check-format)
The operation was canceled.
xtask (run-bazel-tests)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.