R CMD CHECK not working on oldrel version of R

I have uploaded an R package to GitHub and used the GitHub Actions from r-lib/actions to run R CMD CHECK to assess whether my package works. It runs on builds of Windows/Mac/Linux and 6 versions of R.

On 7 out of the 8 builds, it worked fine, but on the ubuntu-16.04 (oldrel) version it has failed in the Run r-lib/actions/setup-r@v1 step. From my (very limited) understanding, this means that it was unable to install the oldrel version of R on ubuntu-16.04. The ubuntu-16.04 build is the only build that gets the oldrel version of R tested on it, so I think the error is specific to installing the R version and not necessarily the OS build.

The output is as follows:

Run r-lib/actions/setup-r@v1
  with:
    r-version: oldrel
    rtools-version: 35
    Ncpus: 1
    crayon.enabled: TRUE
    remove-openmp-macos: true
  env:
    R_REMOTES_NO_ERRORS_FROM_WARNINGS: true
    RSPM: https://packagemanager.rstudio.com/cran/__linux__/xenial/latest
    GITHUB_PAT: ***

To me, this does not actually seem to display an error. The next step (to install pandoc with Run r-lib/actions/setup-pandoc@v1) is not run.

A link to the action as it was most recently run is here.
Be aware, that as I’m unsure what is causing this issue I will be manually re-running this action and so if you follow this link, it may not have completed. If it runs successfully, I will delete this post.

@MyKo101,

I don’t think the problem is on the ubuntu-16.04 OS.
I tested the “r-lib/actions/setup-r@v1” action on multiple OSs (macOS-latest, windows-latest, ubuntu-16.04 and ubuntu-latest), this action is failed on all these OSs when set r-version to be oldrel. More details about the example I tested, see here.

Generally, the R version oldrel (r-oldrel) is the latest version of the previous minor version.
I think the problem is on the setup-r action itself. This action seems does not recognize the right R version which r-oldrel corresponds to, and causes failure to setup the R environment.

I have helped you report an issue ticket (r-lib/actions#123) to the appropriate engineering team on “r-lib/actions” repository.
You can follow that issue ticket and add your comment here.