On 1/2/23 12:38 PM, Dirk Eddelbuettel wrote:
As the error is common against your _all three_ of your Ubuntu runs, you
could consider the possibility that the events are correlated. Most often it
simply means a (temporary, usually) network or server outage. I would wait,
and then relaunch (which these days you can do just for the failed jobs).
It is also worth paying attention to warnings such as
Warning: r-lib/actions/setup-r@v1 is deprecated. Please update your
workflow to use the 'v2' version. Also look at the examples at
https://github.com/r-lib/actions/tree/v2/examples because '@v2' workflows
are much simpler than 'v1' workflows.
Thanks to Zhian Kamvar and Dirk Eddelbuettel for encouraging me to
look at the warning.
I replaced a few lined of my "R-CMD-check.yaml" file with the the
"v3" and "v2" versions in the example in
"https://github.com/r-lib/actions/tree/v2/examples"; and deleted
subsequent lines that I didn't understand, and I got an instant failure:
It didn't run even one of the 5 tests. Then I did "git revert" with
the version number from GitHub and changed several lines to match the
example with the succeeding yaml code. GitHub Action ran and failed on
all 5 platforms. I did "git revert" with that and changed
"r-lib/actions/setup-r@v1" to "r-lib/actions/setup-r@v2". With that,
R-release ran successfully on Unbuntu as well as Windows and macOS.
However, Ubuntu failed with devel and oldrel1, complaining, "there is
no package called ‘rcmdcheck’".
See:
https://github.com/sbgraves237/sos
Suggestions?
Thanks,
Spencer Graves
Hth, Dirk
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
