Skip to content
R-CMD-check

New "aRtsy" pattern (#89) #84

Sign in to view logs

New "aRtsy" pattern (#89)

New "aRtsy" pattern (#89) #84

Triggered via push October 11, 2024 20:23
@trevorldtrevorld
pushed e61edad
main
Status Success
Total duration 24m 15s
Artifacts –

R-CMD-check.yaml

on: push
Matrix: R-CMD-check
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
ubuntu-latest (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-latest (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-latest (oldrel-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-latest (oldrel-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-latest (devel)
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-latest (devel)
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.