Skip to content
pytest

return results instead of none when CODS soiling signal is small #1193

Sign in to view logs

return results instead of none when CODS soiling signal is small

return results instead of none when CODS soiling signal is small #1193

Triggered via pull request November 17, 2023 19:41
@martin-springermartin-springer
synchronize #400
fix_CODS_small_soiling_signal_return
Status Failure
Total duration 10m 30s
Artifacts –

pytest.yaml

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

Annotations

7 errors and 8 warnings
build (3.10, --upgrade --upgrade-strategy=eager .[test])
Process completed with exit code 1.
build (3.8, -r requirements.txt .[test])
The operation was canceled.
build (3.9, --upgrade --upgrade-strategy=eager .[test])
The operation was canceled.
build (3.8, --upgrade --upgrade-strategy=eager .[test])
The operation was canceled.
build (3.7, --upgrade --upgrade-strategy=eager .[test])
The operation was canceled.
build (3.9, -r requirements.txt .[test])
The operation was canceled.
build (3.7, -r requirements-min.txt .[test])
The operation was canceled.
build (3.10, -r requirements.txt .[test])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.10, --upgrade --upgrade-strategy=eager .[test])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.8, -r requirements.txt .[test])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9, --upgrade --upgrade-strategy=eager .[test])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.8, --upgrade --upgrade-strategy=eager .[test])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.7, --upgrade --upgrade-strategy=eager .[test])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9, -r requirements.txt .[test])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.7, -r requirements-min.txt .[test])
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/