Skip to content

fix: use requirements files with hashes instead of constraints #15951

fix: use requirements files with hashes instead of constraints

fix: use requirements files with hashes instead of constraints #15951

Triggered via pull request June 22, 2026 22:01
Status Failure
Total duration 1m 4s
Artifacts

unittest.yml

on: pull_request
Matrix: unit
cover
cover
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
unit (3.13)
Process completed with exit code 1.
unit (3.11)
The strategy configuration was canceled because "unit._3_13" failed
unit (3.11)
The operation was canceled.
unit (3.10)
The strategy configuration was canceled because "unit._3_13" failed
unit (3.10)
The operation was canceled.
unit (3.12)
The strategy configuration was canceled because "unit._3_13" failed
unit (3.12)
The operation was canceled.
unit (3.14)
The strategy configuration was canceled because "unit._3_13" failed
unit (3.14)
The operation was canceled.
unit (3.9)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit (3.9)
No files were found with the provided path: .coverage-3.9. No artifacts will be uploaded.