Event loop is closed

Canceling since a higher priority waiting request for unit-refs/heads/main-3.10 exists

Canceling since a higher priority waiting request for unit-refs/heads/main-3.8 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.13-proto4 exists

Canceling since a higher priority waiting request for unit-refs/heads/main-3.12 exists

Canceling since a higher priority waiting request for unit-refs/heads/main-3.9 exists

Canceling since a higher priority waiting request for unit-refs/heads/main-3.13 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.13-proto3 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.10-proto3 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.12-proto3 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.8-proto5 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.9-proto3 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.8-proto4 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.12-proto6 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.11-proto3 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.9-proto5 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.13-proto6 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.11-proto4 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.9-proto4 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.13-proto5 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.10-proto4 exists

Canceling since a higher priority waiting request for integration-refs/heads/main-3.12-proto5 exists

A task was canceled.

Canceling since a higher priority waiting request for integration-refs/heads/main-3.10-proto6 exists

The operation was canceled.

The operation was canceled.

Canceling since a higher priority waiting request for integration-refs/heads/main-3.11-proto5 exists

The operation was canceled.

Canceling since a higher priority waiting request for integration-refs/heads/main-3.12-proto4 exists

The operation was canceled.

Canceling since a higher priority waiting request for integration-refs/heads/main-3.10-proto5 exists

The operation was canceled.

Canceling since a higher priority waiting request for integration-refs/heads/main-3.11-proto6 exists

The operation was canceled.

Canceling since a higher priority waiting request for integration-refs/heads/main-3.9-proto6 exists

The operation was canceled.

Canceling since a higher priority waiting request for integration-refs/heads/main-3.8-proto3 exists

The operation was canceled.

Canceling since a higher priority waiting request for integration-refs/heads/main-3.8-proto6 exists

The operation was canceled.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v2. 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/