You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All call-r-cmd-check GHA operations from a few feature branches failed. The operations were canceled on windows, macOS, ubuntu after running for a few hours.
However, the R-cmd-check from the 180-feat-population branch and other branches that are based on the population module branch still take over 6 hours to run and fail to run after checking examples.
The error relates to examples from the io.R file. After using \dontrun for the example in the io.R file, the r-cmd-check workflow works again (see working workflows here). Maybe we can
pull the changes from the bug-r-cmd-check-population-modules to 180-feat-population to allow r-cmd-check checks other things (e.g., code compilation and tests for other R functions).
then create a new yml file to run mkObj() only to remind us that we need to figure out why MakeADFun does not work.
Describe the bug
All call-r-cmd-check GHA operations from a few feature branches failed. The operations were canceled on windows, macOS, ubuntu after running for a few hours.
The warning messages include:
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout, actions/checkout
macOS-latest pipelines will use macOS-12 soon. For more details, see actions/runner-images#6384
Relevant issue from the ghactions4r package: nmfs-fish-tools/ghactions4r#46
To Reproduce
GHA logs can be found here and here.
Expected behavior
call-r-cmd-check GHA passes.
Screenshots
No response
Which OS are you seeing the problem on?
Windows, Mac, Linux
Which browser are you seeing the problem on?
No response
Which version of FIMS are you seeing the problem on?
No response
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: