Skip to content
Test

Fix bug in TIMS²Rescore configuration priority #437

Sign in to view logs

Fix bug in TIMS²Rescore configuration priority

Fix bug in TIMS²Rescore configuration priority #437

Triggered via pull request August 14, 2024 11:54
@RalfGRalfG
opened #176
fix/timsrescore-defaults-priority
Status Success
Total duration 1m 54s
Artifacts –

test.yml

on: pull_request
test-windows-installer
0s
test-windows-installer
Matrix: test-python-package
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test-python-package (3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-python-package (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-python-package (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-python-package (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/