-
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
[macOS] Some tests fail [ FAIL 5 | WARN 0 | SKIP 0 | PASS 177 ] #112
Comments
@barracuda156 sorry, im a bit confused. what is the context for this? where is it being run? on what package? |
Ok, so it seems like you're trying to run |
Also, please make sure to use the provided bug template, rather than deleting it. |
Sorry for not being clear. I am adding R packages to Macports and test them whenever tests are provided. When something fails, I normally notify the upstream, since a) there may be an interest to fix it generally (provided it is indeed a bug), and b) if it is not a bug, but an error on our side, I could fix that, following recommendations from upstream, if there are any. |
Ok, thanks for that. I'm not familiar with Macports, could you provide some background describe and how it relates to
|
@barracuda156 without further information, my best guess is that your issue stems from which directory and environment you're running the |
@bschilder Sorry, I was just too busy with other stuff. Macports runs tests from a dedicated directory.
|
@bschilder P. S. I will fill a template today, apologize for missing on that. (I need to get to the machine to do it, now on mobile.) |
1. Bug descriptionWhen running test for Console output
Expected behaviourTests should pass. 2. Reproducible exampleCode
Data(If possible, upload a small sample of your data so that we can reproduce the bug on our end. If that's not possible, please at least include a screenshot of your data and other relevant details.) 3. Session info(Add output of the R function
Port can be found at: https://ports.macports.org/port/R-rworkflows |
Session info:
|
Just in case, I also get these errors on Sonoma, so it is unrelated to either old macOS SDK or powerpc arch:
|
Thanks for the detailed report and apologies for just getting to this now. I'm not sure how exactly The directory structure is important for some test expectations that deal with finding DESCRIPTION files, which yield a different result if you're in the main directory of the cloned package vs. in a separate I've identified all points in tests where this can occur and added conditional test skips. I validated this solution by running > devtools::test_coverage()
ℹ Computing test coverage for rworkflows |
The text was updated successfully, but these errors were encountered: