Skip to content

Drop Python 3.9 compat in build: bump to 3.10 and keep importlib-meta… #12964

Drop Python 3.9 compat in build: bump to 3.10 and keep importlib-meta…

Drop Python 3.9 compat in build: bump to 3.10 and keep importlib-meta… #12964

Re-run triggered March 30, 2026 22:21
Status Failure
Total duration 10m 13s
Artifacts –

pr-check.yml

on: push
Matrix: Create VSIX
Matrix: Native Tests
Matrix: Python Tests
Matrix: Tests
Lint
59s
Lint
Check Python types
46s
Check Python types
Matrix: Smoke tests
Matrix: Coverage
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 8 warnings
Python Tests (ubuntu-latest, 3.9, pytest==6.2.0)
Process completed with exit code 1.
Python Tests (ubuntu-latest, 3.9, pytest@pre-release)
Process completed with exit code 1.
Python Tests (ubuntu-latest, 3.9, pytest)
Process completed with exit code 1.
Lint
Process completed with exit code 1.
Python Tests (windows-latest, 3.9, pytest@pre-release)
Process completed with exit code 1.
Python Tests (windows-latest, 3.9, pytest)
Process completed with exit code 1.
Python Tests (windows-latest, 3.9, pytest==6.2.0)
Process completed with exit code 1.
Tests (ubuntu-latest, 3.x, debugger)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: GabrielBB/xvfb-action@b706e4e27b14669b486812790492dc50ca16b465. 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/
Tests (ubuntu-latest, 3.x, venv)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: GabrielBB/xvfb-action@b706e4e27b14669b486812790492dc50ca16b465. 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/
Tests (ubuntu-latest, 3.x, single-workspace)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: GabrielBB/xvfb-action@b706e4e27b14669b486812790492dc50ca16b465. 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/
Tests (windows-latest, 3.x, debugger)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: GabrielBB/xvfb-action@b706e4e27b14669b486812790492dc50ca16b465. 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/
Tests (windows-latest, 3.x, venv)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: GabrielBB/xvfb-action@b706e4e27b14669b486812790492dc50ca16b465. 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/
Smoke tests (ubuntu-latest, linux-x64)
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/setup-node@v4, actions/setup-python@v5, GabrielBB/xvfb-action@b706e4e27b14669b486812790492dc50ca16b465. 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/
Tests (windows-latest, 3.x, single-workspace)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: GabrielBB/xvfb-action@b706e4e27b14669b486812790492dc50ca16b465. 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/
Smoke tests (windows-latest, win32-x64)
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/setup-node@v4, actions/setup-python@v5, GabrielBB/xvfb-action@b706e4e27b14669b486812790492dc50ca16b465. 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/