Skip to content

beginning of something to have relative, absolute or binary freqs #114

beginning of something to have relative, absolute or binary freqs

beginning of something to have relative, absolute or binary freqs #114

Triggered via pull request October 21, 2024 13:50
Status Failure
Total duration 53s
Artifacts

python-package.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
build (3.11)
Process completed with exit code 1.
build (3.10)
Process completed with exit code 1.
build (3.9)
Process completed with exit code 1.
build (3.12)
Process completed with exit code 1.
build (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (3.12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/