Skip to content

[dotnet] [bidi] Don't propagate cancellation token for websocket #20831

[dotnet] [bidi] Don't propagate cancellation token for websocket

[dotnet] [bidi] Don't propagate cancellation token for websocket #20831

Triggered via pull request March 13, 2026 12:36
Status Success
Total duration 17m 56s
Artifacts –

ci.yml

on: pull_request
Build Index  /  ...  /  bazel
Build Index / Build Test Index / bazel
Check Targets  /  Check Targets
1m 12s
Check Targets / Check Targets
Build Index  /  Cache Index
Build Index / Cache Index
Read Targets
4s
Read Targets
Python  /  ...  /  bazel
Python / Build / bazel
Ruby  /  ...  /  bazel
Ruby / Build / bazel
Rust  /  ...  /  bazel
Rust / Build / bazel
.NET  /  ...  /  Lint
12m 49s
.NET / Lint / Lint
.NET  /  ...  /  Build
14m 32s
.NET / Build / Build
.NET  /  ...  /  Browser Tests
13m 26s
.NET / Browser Tests / Browser Tests
.NET  /  ...  /  Remote Tests
16m 30s
.NET / Remote Tests / Remote Tests
Python  /  ...  /  bazel
Python / Lint / 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
Python / Remote Tests / bazel
Matrix: Python / Browser Tests
Waiting for pending jobs
Matrix: Python / Unit Tests
Waiting for pending jobs
Ruby  /  ...  /  bazel
Ruby / Lint / 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 Debug
Rust  /  Linux Stable
Rust / Linux Stable
Rust  /  MacOS Debug
Rust / MacOS Debug
Rust  /  MacOS Stable
Rust / MacOS Stable
Rust  /  Windows Debug
Rust / Windows Debug
Rust  /  Windows Stable
Rust / Windows Stable
Rust  /  Release Binaries
Rust / Release Binaries
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
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. 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. 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/
.NET / 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, bazel-contrib/setup-bazel@0.18.0. 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/
.NET / Browser Tests / Browser Tests
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.18.0. 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/
.NET / 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, bazel-contrib/setup-bazel@0.18.0. 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/
.NET / Remote Tests / Remote Tests
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.18.0. 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/