No public description #162
ubuntu-build.yml
on: pull_request
Matrix: bazel_inner
ubuntu-latest cmake
1m 6s
ubuntu-latest bazel
Annotations
3 errors and 22 warnings
|
bazel c++20
Process completed with exit code 1.
|
|
bazel c++14
Process completed with exit code 1.
|
|
bazel c++17
Process completed with exit code 1.
|
|
bazel c++20
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5, bazel-contrib/setup-bazel@0.8.4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
bazel c++20
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ZZlKagAAAAAS0uej4YXjTKROMgM4ZmAqUEhMMzBFREdFMDIxMwBFZGdl
|
|
bazel c++20
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ZZlKagAAAADTL70GsobKQYtPW/bwbZP5UEhMMzBFREdFMDIxMwBFZGdl
|
|
bazel c++20
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ZZlKagAAAAC9tDtuWwkyR48BZonTQr//UEhMMzBFREdFMDIxMwBFZGdl
|
|
bazel c++20
Failed to restore: Cache service responded with 400
|
|
bazel c++20
Failed to restore: Cache service responded with 400
|
|
bazel c++20
Failed to restore: Cache service responded with 400
|
|
bazel c++14
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5, bazel-contrib/setup-bazel@0.8.4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
bazel c++14
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0cZlKagAAAABIjzItaHneT5NSQmhQVhIHTEFYMzExMDAwMTE0MDIzAEVkZ2U=
|
|
bazel c++14
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0cJlKagAAAABysQp2EVWbTomAlapgtu9OTEFYMzExMDAwMTE0MDIzAEVkZ2U=
|
|
bazel c++14
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0cJlKagAAAAANy8IF0squSLJaZFORaQ8tTEFYMzExMDAwMTE0MDIzAEVkZ2U=
|
|
bazel c++14
Failed to restore: Cache service responded with 400
|
|
bazel c++14
Failed to restore: Cache service responded with 400
|
|
bazel c++14
Failed to restore: Cache service responded with 400
|
|
bazel c++17
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5, bazel-contrib/setup-bazel@0.8.4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
bazel c++17
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0fZlKagAAAADNY4nSGGlHRL3rw/qcX45eU0xDMzFFREdFMDIxNABFZGdl
|
|
bazel c++17
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0fJlKagAAAAAat6XJZ+VpQayxCTJW73diU0xDMzFFREdFMDIxNABFZGdl
|
|
bazel c++17
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0fJlKagAAAAAeOnEyRRPTR5SsZ6b8AOwAU0xDMzFFREdFMDIxNABFZGdl
|
|
bazel c++17
Failed to restore: Cache service responded with 400
|
|
bazel c++17
Failed to restore: Cache service responded with 400
|
|
bazel c++17
Failed to restore: Cache service responded with 400
|
|
ubuntu-latest cmake
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|