Skip to content

QC comment functionality and testing #84

QC comment functionality and testing

QC comment functionality and testing #84

Triggered via pull request October 25, 2024 18:52
Status Failure
Total duration 5m 50s
Artifacts

main.yaml

on: pull_request
Matrix: check
Upload release
0s
Upload release
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 warnings
ubuntu-latest R release
Process completed with exit code 1.
ubuntu-20.04 R 4.2.3
Process completed with exit code 1.
ubuntu-20.04 R 4.3.1
Process completed with exit code 1.
ubuntu-20.04 R 4.1.3
Process completed with exit code 1.
ubuntu-20.04 R 4.0.5
Process completed with exit code 1.
ubuntu-latest R release
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
ubuntu-20.04 R 4.2.3
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
ubuntu-20.04 R 4.3.1
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
ubuntu-20.04 R 4.1.3
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
ubuntu-20.04 R 4.0.5
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.