Skip to content

Improve valgrind CI check #244

Improve valgrind CI check

Improve valgrind CI check #244

Triggered via pull request October 20, 2023 13:02
@r-ashr-ash
synchronize #37
valgrind-ci
Status Failure
Total duration 6m 37s
Artifacts 1

R-CMD-check.yaml

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

Annotations

2 errors and 5 warnings
macOS-latest (release)
R CMD check found ERRORs
macOS-latest (release)
Process completed with exit code 1.
ubuntu-latest (devel)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ubuntu-latest (release)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
macOS-latest (release)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
windows-latest (release)
file 'frogger/inst/standalone_model/configure' did not have execute permissions: corrected
windows-latest (release)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
macOS-rrelease-results Expired
20.7 MB