Re: [R-pkg-devel] Current recommendations re. GitHub Action?
On Mon, 2 Jan 2023 19:18:33 -0600 Spencer Graves wrote: > However, Ubuntu failed with devel and oldrel1, complaining, > "there is no package called ‘rcmdcheck’". If we start from the error message and work backwards, it's easy to see that `rcmdcheck` fails to install because it depends on `curl`, which also fails to install. `curl` fails to install because the virtual machine running the GitHub Action doesn't have libcurl headers installed; there's even an error message about that, but it's not fatal: - ANTICONF ERROR --- Configuration failed because libcurl was not found. Try installing: * deb: libcurl4-openssl-dev (Debian, Ubuntu, etc) * rpm: libcurl-devel (Fedora, CentOS, RHEL) If libcurl is already installed, check that 'pkg-config' is in your PATH and PKG_CONFIG_PATH contains a libcurl.pc file. If pkg-config is unavailable you can set INCLUDE_DIR and LIB_DIR manually via: R CMD INSTALL --configure-vars='INCLUDE_DIR=... LIB_DIR=...' I don't have enough experience in the abstraction layers involved, but if you stuff a `sudo apt install libcurl4-openssl-dev` (which should run as a system command line, just like the "Install system dependencies" step) somewhere before the "Install dependencies" step, it should work. -- Best regards, Ivan __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Current recommendations re. GitHub Action?
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
Re: [R-pkg-devel] Current recommendations re. GitHub Action?
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. Hth, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Current recommendations re. GitHub Action?
This warning says to update to v2 of the action from r-lib: 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. We ran into a similar problem and switching to v2 did the trick. Best, Zhian On Mon, Jan 2, 2023 at 10:20 AM Spencer Graves < spencer.gra...@effectivedefense.org> wrote: > Hello, All: > > > What are current recommendations for GitHub Action? > > > My most recent change to "sos" generated "Failed to get R" for > ubuntu-latest (release, devel, and oldrel-1). > > > https://github.com/sbgraves237/sos/actions/runs/3820307473/jobs/6498527786 > > > I would happily rtfm if I only knew which fmtr. > > > Thanks, > Spencer Graves > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Current recommendations re. GitHub Action?
Hello, All: What are current recommendations for GitHub Action? My most recent change to "sos" generated "Failed to get R" for ubuntu-latest (release, devel, and oldrel-1). https://github.com/sbgraves237/sos/actions/runs/3820307473/jobs/6498527786 I would happily rtfm if I only knew which fmtr. Thanks, Spencer Graves __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
