Skip to content

Updated DBs and analizer #53

Updated DBs and analizer

Updated DBs and analizer #53

Triggered via pull request March 20, 2026 14:41
Status Failure
Total duration 31s
Artifacts

python-package.yml

on: pull_request
Matrix: build-os-latest
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 6 warnings
build-os-latest (ubuntu-latest, 3.11, pytest)
Process completed with exit code 1.
build-os-latest (macos-latest, 3.11, pytest)
The strategy configuration was canceled because "build-os-latest.ubuntu-latest_3_11_pytest" failed
build-os-latest (macos-latest, 3.11, pytest)
The operation was canceled.
build-os-latest (macos-latest, 3.10, pytest)
The strategy configuration was canceled because "build-os-latest.ubuntu-latest_3_11_pytest" failed
build-os-latest (macos-latest, 3.10, pytest)
The operation was canceled.
build-os-latest (ubuntu-latest, 3.12, pytest)
The strategy configuration was canceled because "build-os-latest.ubuntu-latest_3_11_pytest" failed
build-os-latest (ubuntu-latest, 3.12, pytest)
The operation was canceled.
build-os-latest (ubuntu-latest, 3.13, pytest)
The strategy configuration was canceled because "build-os-latest.ubuntu-latest_3_11_pytest" failed
build-os-latest (ubuntu-latest, 3.13, pytest)
The operation was canceled.
build-os-latest (ubuntu-latest, 3.10, pytest)
The strategy configuration was canceled because "build-os-latest.ubuntu-latest_3_11_pytest" failed
build-os-latest (ubuntu-latest, 3.10, pytest)
The operation was canceled.
build-os-latest (ubuntu-latest, 3.11, pytest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
build-os-latest (macos-latest, 3.11, pytest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
build-os-latest (macos-latest, 3.10, pytest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
build-os-latest (ubuntu-latest, 3.12, pytest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
build-os-latest (ubuntu-latest, 3.13, pytest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/
build-os-latest (ubuntu-latest, 3.10, pytest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. 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/