Repository navigation
[py] fix linting and mypy to properly exclude generated bidi files #21782
ci.yml
on: pull_request
Build Index
/
...
/
bazel
Check Targets
/
Check Targets
4m 21s
Build Index
/
Cache Index
Python
/
...
/
Lint
45s
.NET
/
...
/
bazel
.NET
/
...
/
bazel
.NET
/
...
/
bazel
.NET
/
...
/
bazel
Grid
/
...
/
bazel
Matrix: Java / Browser Tests
Waiting for pending jobs
Matrix: Java / Browser Tests
Waiting for pending jobs
Matrix: Java / Remote Tests
Waiting for pending jobs
Python
/
...
/
bazel
Matrix: Python / Browser Tests
Waiting for pending jobs
Matrix: Python / Unit Tests
Waiting for pending jobs
Ruby
/
...
/
bazel
Matrix: Ruby / Local Tests
Waiting for pending jobs
Matrix: Ruby / Unit Tests
Waiting for pending jobs
Matrix: Rust / Tests
Waiting for pending jobs
Rust
/
Linux Debug
Rust
/
Linux Stable
Rust
/
MacOS Debug
Rust
/
MacOS Stable
Rust
/
Windows Debug
Rust
/
Windows Stable
Rust
/
Release Binaries
Annotations
12 errors and 6 warnings
|
Python / Build / Build
Process completed with exit code 127.
|
|
Python / Build / Build
Process completed with exit code 127.
|
|
Python / Build / Build
The process '/usr/bin/git' failed with exit code 128
|
|
Python / Build / Build
couldn't find remote ref refs/pull/17433/merge
|
|
Python / Build / Build
couldn't find remote ref refs/pull/17433/merge
|
|
Python / Build / Build
couldn't find remote ref refs/pull/17433/merge
|
|
Python / Lint / Lint
Process completed with exit code 127.
|
|
Python / Lint / Lint
Process completed with exit code 127.
|
|
Python / Lint / Lint
The process '/usr/bin/git' failed with exit code 128
|
|
Python / Lint / Lint
couldn't find remote ref refs/pull/17433/merge
|
|
Python / Lint / Lint
couldn't find remote ref refs/pull/17433/merge
|
|
Python / Lint / Lint
couldn't find remote ref refs/pull/17433/merge
|
|
Check Targets / Check Targets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/upload-artifact@v5, bazel-contrib/setup-bazel@0.18.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Read Targets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Python / Build / Build
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/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Python / Build / Build
No files were found with the provided path: build/failures/**. No artifacts will be uploaded.
|
|
Python / Lint / Lint
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/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Python / Lint / Lint
No files were found with the provided path: build/failures/**. No artifacts will be uploaded.
|