-
Notifications
You must be signed in to change notification settings - Fork 7
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
Bioc rworkflows fail #130
Comments
The timing suggests this may be due to the recent release of Bioc 3.19 There's always a lag between the Bioc release cycle and the Bioc Docker container update: |
Bioc/R versions picked by rworkflows::bioc_r_versions()
|
Alright, thanks. That sounds exactly how it should be. However, the error messages suggested mismatch between R versions. We check if we can fix our workflow issue |
I agree, the specific message you reported does still have me a bit puzzled. |
We are trying to troubleshoot the problem in this PR microbiome/mia#544 The documentation of rworkflows indicates that secrets are needed for some options such as Docker (we have not enabled it yet). We have been using rworkflows for a while, and it has worked before. Has something changed because it seems that github-actions does not have access anymore to deploy documentation (we have not had secrets before either)?
|
We were able to solve the issue. Something related to cache and this R/Bioc cycle. That permission thing resolved when the build was run in devel branch. |
Hello!
We are using rworkflows in our Bioconductor packages. We noticed maybe week ago that Ubuntu (and MAC) workflow started to fail; we did not do any changes. We thought that the problem might resolve itself, but it has not.
Here is our workflow: https://github.com/microbiome/mia/blob/devel/.github/workflows/rworkflows.yml
Here is the result of the workflow run: https://github.com/microbiome/mia/actions/runs/8935442827/job/24543956269
I have not been able to fix the problem, but it seems that:
Bioconductor development should be done against R-release (R-4.4.0) currently. So it seems that rworkflows picks the wrong R version which causes this problem (some packages are built in R-4.4.0 and some in R-4.5.0).
Thanks in advance!
BR,
Tuomas Borman
The text was updated successfully, but these errors were encountered: