ci: cap gevent for free-threaded Python #2239
Annotations
36 errors and 17 warnings
|
test libev (3.13)
cannot schedule new futures after shutdown
|
|
test libev (3.13)
cannot schedule new futures after shutdown
|
|
test libev (3.13)
cannot schedule new futures after shutdown
|
|
test libev (3.13)
cannot schedule new futures after shutdown
|
|
test libev (3.12)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test asyncio (3.13)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14)
cannot schedule new futures after shutdown
|
|
test libev (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.11)
cannot schedule new futures after shutdown
|
|
test libev (3.11)
cannot schedule new futures after shutdown
|
|
test libev (3.11)
cannot schedule new futures after shutdown
|
|
test libev (3.11)
cannot schedule new futures after shutdown
|
|
test asyncore (3.11)
cannot schedule new futures after shutdown
|
|
test asyncore (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.11):
cassandra/cluster.py#L4343
cannot schedule new futures after shutdown
|
|
test asyncio (3.11)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test asyncio (3.14t)
cannot schedule new futures after shutdown
|
|
test libev (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test libev (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test asyncio (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test asyncio (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test asyncio (3.13)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.13-pruned-8adc66e1c445e77446600bd78e81c2705577d74f889d6d4aa26c219ca1a493ad, another job may be creating this cache.
|
|
test asyncio (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test asyncio (3.12)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12-pruned-8adc66e1c445e77446600bd78e81c2705577d74f889d6d4aa26c219ca1a493ad, another job may be creating this cache.
|
|
test libev (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test libev (3.14)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.14-pruned-8adc66e1c445e77446600bd78e81c2705577d74f889d6d4aa26c219ca1a493ad, another job may be creating this cache.
|
|
test libev (3.14t)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test libev (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test asyncore (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test asyncore (3.11)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.11-pruned-8adc66e1c445e77446600bd78e81c2705577d74f889d6d4aa26c219ca1a493ad, another job may be creating this cache.
|
|
test asyncio (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test asyncio (3.11)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.11-pruned-8adc66e1c445e77446600bd78e81c2705577d74f889d6d4aa26c219ca1a493ad, another job may be creating this cache.
|
|
test asyncio (3.14t)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
test asyncio (3.14t)
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.14t-pruned-8adc66e1c445e77446600bd78e81c2705577d74f889d6d4aa26c219ca1a493ad, another job may be creating this cache.
|