Skip to content

Bump black from 24.8.0 to 26.3.1 in the pip group across 1 directory #111

Bump black from 24.8.0 to 26.3.1 in the pip group across 1 directory

Bump black from 24.8.0 to 26.3.1 in the pip group across 1 directory #111

Triggered via pull request March 12, 2026 20:47
Status Failure
Total duration 1m 3s
Artifacts

verify-pull-request.yml

on: pull_request
Check Python formatting
13s
Check Python formatting
Check build.json
16s
Check build.json
Matrix: Run Bazel tests
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 36 warnings
Run Bazel tests (clang, -c opt)
Process completed with exit code 1.
Run Bazel tests (gcc, -c opt)
The strategy configuration was canceled because "run-bazel-tests.clang_-c_opt" failed
Run Bazel tests (gcc, -c opt)
The operation was canceled.
Run Bazel tests (clang)
The strategy configuration was canceled because "run-bazel-tests.clang_-c_opt" failed
Run Bazel tests (clang)
The operation was canceled.
Run Bazel tests (gcc)
The strategy configuration was canceled because "run-bazel-tests.clang_-c_opt" failed
Run Bazel tests (gcc)
The operation was canceled.
Check Python formatting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check build.json
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, bazel-contrib/setup-bazel@0.8.5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check build.json
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at Object.<anonymous> (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.8.5/dist/node_modules/@actions/cache/lib/cache.js:175:1) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.8.5/dist/node_modules/@actions/cache/lib/cache.js:28:1)
Check build.json
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at Object.<anonymous> (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.8.5/dist/node_modules/@actions/cache/lib/cache.js:175:1) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.8.5/dist/node_modules/@actions/cache/lib/cache.js:28:1)
Check build.json
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>0diazaQAAAABQiUAKpCZLRIcmVZlEoTx7UEhMMzBFREdFMDIxMwBFZGdl
Check build.json
Failed to restore: Cache service responded with 400
Check build.json
Failed to restore: Cache service responded with 400
Check build.json
Failed to restore: Cache service responded with 400
Run Bazel tests (clang, -c opt)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, bazel-contrib/setup-bazel@0.8.5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Bazel tests (clang, -c opt)
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>0jiazaQAAAAApizlhJQtlS49X6g+B1hiNREVOMzAxMDAwMTA3MDQ5AEVkZ2U=
Run Bazel tests (clang, -c opt)
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>0jSazaQAAAADXJ6SjzacASbfxH5IgJmOLREVOMzAxMDAwMTA3MDQ5AEVkZ2U=
Run Bazel tests (clang, -c opt)
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>0jSazaQAAAADvGE9DJgiORrkdKl2yzsakREVOMzAxMDAwMTA3MDQ5AEVkZ2U=
Run Bazel tests (clang, -c opt)
Failed to restore: Cache service responded with 400
Run Bazel tests (clang, -c opt)
Failed to restore: Cache service responded with 400
Run Bazel tests (clang, -c opt)
Failed to restore: Cache service responded with 400
Run Bazel tests (gcc, -c opt)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, bazel-contrib/setup-bazel@0.8.5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Bazel tests (gcc, -c opt)
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>0mCazaQAAAAAYLO9vtJ0TQbuP3lTy120WRE0yRURHRTA5MDgARWRnZQ==
Run Bazel tests (gcc, -c opt)
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>0lyazaQAAAABsxMUpbTqmTKHyiWho4fRZRE0yRURHRTA5MDgARWRnZQ==
Run Bazel tests (gcc, -c opt)
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>0lyazaQAAAADQq6M3Z6GAQpftZ7yAKosFRE0yRURHRTA5MDgARWRnZQ==
Run Bazel tests (gcc, -c opt)
Failed to restore: Cache service responded with 400
Run Bazel tests (gcc, -c opt)
Failed to restore: Cache service responded with 400
Run Bazel tests (gcc, -c opt)
Failed to restore: Cache service responded with 400
Run Bazel tests (clang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, bazel-contrib/setup-bazel@0.8.5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Bazel tests (clang)
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>0niazaQAAAABZNCTCoRbqSLdDpHnQCWLnRE0yRURHRTA5MTgARWRnZQ==
Run Bazel tests (clang)
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>0nSazaQAAAADSfNyPkDU3S7J8GLfwqgOPRE0yRURHRTA5MTgARWRnZQ==
Run Bazel tests (clang)
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>0nSazaQAAAADukGXWpCbqQoWnRFgo51iaRE0yRURHRTA5MTgARWRnZQ==
Run Bazel tests (clang)
Failed to restore: Cache service responded with 400
Run Bazel tests (clang)
Failed to restore: Cache service responded with 400
Run Bazel tests (clang)
Failed to restore: Cache service responded with 400
Run Bazel tests (gcc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, bazel-contrib/setup-bazel@0.8.5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Bazel tests (gcc)
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>0oCazaQAAAADMLanlQwIKT6o+MFwo5fmyUEhYMzFFREdFMDUxNQBFZGdl
Run Bazel tests (gcc)
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>0nyazaQAAAACP7ucxk64OSK5hqCsK49qcUEhYMzFFREdFMDUxNQBFZGdl
Run Bazel tests (gcc)
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>0niazaQAAAADssgCKmIjFTLTLdVQhnpGvUEhYMzFFREdFMDUxNQBFZGdl
Run Bazel tests (gcc)
Failed to restore: Cache service responded with 400
Run Bazel tests (gcc)
Failed to restore: Cache service responded with 400
Run Bazel tests (gcc)
Failed to restore: Cache service responded with 400