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
REVDEP: How to disable breaking lifecycle_warning_deprecated warning? #213
Comments
Thanks, I just need to update the snapshot tests. There was a change in testthat related to how condition information is printed out (it no longer shows the class). |
Thanks. I'm curious though, why isn't this showing up on https://cran.r-project.org/web/checks/check_results_furrr.html? |
Because snapshot tests don't run on CRAN (by design). See the
These kinds of tests are useful for us to check the structure of warnings / errors / output. We want to be notified by CI when these kinds of tests change, but they usually aren't mission critical and are a little fragile (because they are very strict in what they test), so we don't want to get kicked off CRAN if one happens to change |
I see - that makes sense. |
Follow-up question: Looking at I've tried that: but it made no difference: https://github.com/HenrikBengtsson/future/actions/runs/3705829844/jobs/6280255577 |
We talked about that over here You want |
Doh. Good, I thought I was going mad making up a memory of you helping me resolve this in the past, but I couldn't find it. Got it working now. Thanks again, and thanks for being a backup to my poor memory |
Hi. When I run revdep checks on future, furrr has been giving be the following test error since quite a while:
For an example, see https://github.com/HenrikBengtsson/future/runs/6104651301?check_suite_focus=true#step:10:102.
Do you know if there is a setting (environment variable or R option) that I can set that prevents this warnings from triggering this error? Alternatively, is this something you need to fix in that check?
The text was updated successfully, but these errors were encountered: