Automated Code Change #511
copybara-service[bot]ubuntu-build.yml
on: push
Matrix: bazel_inner
cmake
5m 32s
bazel
Annotations
3 errors and 22 warnings
|
bazel c++17
Process completed with exit code 1.
|
|
bazel c++14
Process completed with exit code 1.
|
|
bazel c++20
Process completed with exit code 1.
|
|
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>0PGM3agAAAACDWOurjtdoQqtAJ3uwIPhAUEhMMzBFREdFMDIxNQBFZGdl
|
|
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>0O2M3agAAAACHbXoFbScfS51NGtFfnxyVUEhMMzBFREdFMDIxNQBFZGdl
|
|
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>0O2M3agAAAACjLZeshlR0Qpq0fgRdVGSHUEhMMzBFREdFMDIxNQBFZGdl
|
|
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
|
|
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>0Y2M3agAAAABt9LqpsavzQrTGUELWN747Q08xRURHRTI1MTQARWRnZQ==
|
|
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>0Y2M3agAAAAAvuK6BNhUMQK9Ssvu8ee/kQ08xRURHRTI1MTQARWRnZQ==
|
|
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>0Y2M3agAAAAD9kKRr54asSIs2/We+SCNUQ08xRURHRTI1MTQARWRnZQ==
|
|
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++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>0dGM3agAAAAD/akP6L49lSpB8SSOIIQXhUEhYMzFFREdFMDYxOABFZGdl
|
|
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>0dGM3agAAAADJM2EOLp0KTLnplnkGCRa5UEhYMzFFREdFMDYxOABFZGdl
|
|
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>0c2M3agAAAADM6lPjAnTzTKnc3s7N6gBrUEhYMzFFREdFMDYxOABFZGdl
|
|
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
|
|
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/
|