Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macOS-latest (devel) check failure #140

Closed
MyKo101 opened this issue Jul 22, 2020 · 5 comments
Closed

macOS-latest (devel) check failure #140

MyKo101 opened this issue Jul 22, 2020 · 5 comments
Labels
bug an unexpected problem or unintended behavior

Comments

@MyKo101
Copy link

MyKo101 commented Jul 22, 2020

The line

Run r-lib/actions/setup-r@master

is failing on the macOS-latest (devel) build, however it passes on windows-latest (release), macOS-latest (release) and ubuntu-16.04 (release). The last line of the output of the step claims that the install was successful., however the next step is not run.

The only warning I have seen in the output is:

Warning: macOS's Gatekeeper has been disabled for this Cask

Failing Workflow Can Be Seen Here

@MyKo101 MyKo101 added the bug an unexpected problem or unintended behavior label Jul 22, 2020
Sparrow0hawk added a commit to Urban-Analytics/rampuaR that referenced this issue Jul 24, 2020
r versions 3.4, 3.3 removed from matrix as RecordLinkage is not available for those versions

also removed rspm for ubuntu-16.04 r 3.5 due to corrupted ff package

this will still fail due to issues with macOS latest devel (r-lib/actions#140)
Sparrow0hawk added a commit to Urban-Analytics/rampuaR that referenced this issue Jul 24, 2020
changes include:
added quiet = FALSE to workflow to troubleshoot errors
r versions 3.4, 3.3 removed from matrix as RecordLinkage is not available for those versions
will still fail due to issues with macOS latest devel (r-lib/actions#140)
**added conditional statement to only get ff for xenial r3.5 from cran rather than rspm**
@jonkeane
Copy link

It looks like the nightly builds that the action tries to download (from https://mac.r-project.org/high-sierra/R-devel/R-devel.pkg) aren't being posted as expected. Once those are back, the action should work again.

(And I see that there's already #121 to provide a bit more info in circumstances like this.)

Sparrow0hawk added a commit to Urban-Analytics/rampuaR that referenced this issue Jul 30, 2020
changes include:
added quiet = FALSE to workflow to troubleshoot errors
r versions 3.4, 3.3 removed from matrix as RecordLinkage is not available for those versions
will still fail due to issues with macOS latest devel (r-lib/actions#140)
**added conditional statement to only get ff for xenial r3.5 from cran rather than rspm**
jgabry added a commit to stan-dev/bayesplot that referenced this issue Aug 6, 2020
temporarily disable {os: macOS-latest,   r: 'devel'} due to r-lib/actions#140
@igordot
Copy link

igordot commented Aug 8, 2020

After more than two weeks, it looks like this is still a problem. Is there some status page or discussion that might be helpful? Should we just give up on the macOS-latest (devel) build?

jimmyday12 added a commit to jimmyday12/fitzRoy that referenced this issue Aug 9, 2020
Relates to an issue described on the r-lib repo r-lib/actions#140
@jimhester
Copy link
Member

We enquired about this on R-Sig-Mac when this issue was opened, it seems there was an issue with the build machine signing binaries.

Until it is remedied R devel for macOS will be unavailable on GitHub Actions, however as a workaround you can use R devel on Linux or Windows as alternatives.

@aylapear
Copy link

About 7 days ago our macOs-latest (devel) runs started passing again with just a warning. Not sure if it is fixed for good but it is working for us again.

@github-actions
Copy link

github-actions bot commented Nov 7, 2022

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

5 participants