Skip to content

test: replace legacy tmpdir with tmp_path #3468

test: replace legacy tmpdir with tmp_path

test: replace legacy tmpdir with tmp_path #3468

Triggered via pull request March 14, 2026 06:27
Status Failure
Total duration 1m 23s
Artifacts

pythonpackage.yml

on: pull_request
detect_changes
8s
detect_changes
Matrix: python-check
Fit to window
Zoom out
Zoom in

Annotations

28 errors and 2 warnings
python-check (3.10, ubuntu-22.04)
Process completed with exit code 1.
python-check (3.12, ubuntu-22.04)
Process completed with exit code 1.
python-check (3.12, windows-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.12, windows-latest)
The operation was canceled.
python-check (3.14, windows-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.14, windows-latest)
The operation was canceled.
python-check (3.10, macos-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.10, macos-latest)
The operation was canceled.
python-check (3.14, ubuntu-22.04)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.14, ubuntu-22.04)
The operation was canceled.
python-check (3.13, windows-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.13, windows-latest)
The operation was canceled.
python-check (3.10, windows-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.10, windows-latest)
The operation was canceled.
python-check (3.11, windows-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.11, windows-latest)
The operation was canceled.
python-check (3.11, ubuntu-22.04)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.11, ubuntu-22.04)
The operation was canceled.
python-check (3.13, ubuntu-22.04)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.13, ubuntu-22.04)
The operation was canceled.
python-check (3.13, macos-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.13, macos-latest)
The operation was canceled.
python-check (3.14, macos-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.14, macos-latest)
The operation was canceled.
python-check (3.11, macos-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.11, macos-latest)
The operation was canceled.
python-check (3.12, macos-latest)
The strategy configuration was canceled because "python-check._3_10_ubuntu-22_04" failed
python-check (3.12, macos-latest)
The operation was canceled.
python-check (3.10, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
python-check (3.12, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/