Automated Code Change #514
copybara-service[bot]ubuntu-build.yml
on: pull_request
Matrix: bazel_inner
cmake
6m 7s
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>0KDdAagAAAADFArnfedneTL7hg+o9QOT8TVNQMzExMDAwMTA4MDM3AEVkZ2U=
|
|
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>0KDdAagAAAAAgzMtyf2klQp061dlf9RneTVNQMzExMDAwMTA4MDM3AEVkZ2U=
|
|
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>0KDdAagAAAADGdt65dCsHRYprjFoMC2PKTVNQMzExMDAwMTA4MDM3AEVkZ2U=
|
|
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>0WzdAagAAAADf2FTl2cDqQJc0q8JYdGy4TEFYRURHRTE3MjAARWRnZQ==
|
|
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>0WzdAagAAAABeSoL/yTepQpkBIiOqNDFbTEFYRURHRTE3MjAARWRnZQ==
|
|
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>0WzdAagAAAAC7XQWHIGLdSbxr38sy4+l0TEFYRURHRTE3MjAARWRnZQ==
|
|
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>0XDdAagAAAAAJh2T9fOqsRKggPUd2RaM0TEFYMzExMDAwMTA5MDUxAEVkZ2U=
|
|
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>0WzdAagAAAACTDD/+134ZRrzaPbOGc/9QTEFYMzExMDAwMTA5MDUxAEVkZ2U=
|
|
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>0WzdAagAAAABeU+s82XfVRaatx0cAFysCTEFYMzExMDAwMTA5MDUxAEVkZ2U=
|
|
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
|
|
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/
|