Closed IndrajeetPatil closed 2 years ago
Did any tests fail for you? I can see that covrpage_skip was invoked
No, all of my tests succeed locally
== Results ==========================================================
Duration: 172.9 s
OK: 796
Failed: 0
Warnings: 0
Skipped: 0
on Travis
: https://travis-ci.org/IndrajeetPatil/ggstatsplot/builds/657026885
and
on AppVeyor
: https://ci.appveyor.com/project/IndrajeetPatil/ggstatsplot/builds/31165748
on both R 3.6.3
and R 4.0
.
Ok. I’ll try and see what is changing in the R-devel, but it will probably take a while.
Are those local results above from test_dir or test_check?
I confirm the same issue. All tests succeed.
Any plans to have this fixed?
Thanks
Thanks for the update. What repo are you working with?
Thanks for coming back. I am working on private repos and all have the same issue. (R version 4.0.2 (2020-06-22)
.
Another problem is that covrpage
updates the status on the README
but it's false because the process never succeeded. Please see an example on this repo https://github.com/ropenscilabs/tic.covrpage.
Clicking on covrpage status to check the report:
Thanks, can you please open this as a separate issue. I’ll get to this too.
I just don’t want to create issues that have multiple problems, it is harder to track.
Thanks
@IndrajeetPatil I just rebuilt covrpage on 4.0.2 and all tests pass for the package.
I merged your master of ggstatsplot on my fork and ran covrpage and it didnt crash.
It did skip a lot of the tests though do to judicious use of testthat::skip_on_cran()
here is the tests/readme
@Eluvias i'm not sure what you mean by not succeeded, it is passing on travis, thus updating the badge on success.
@yonicd Have you tested it on Windows platform? I am on Windows, the covrpage for ggstatsplot
was run on Windows too.
i'm not sure what you mean by not succeeded, it is passing on travis, thus updating the badge on success.
When I run covrpage::covrpage()
the process runs successfully despite the fact the knitting of _covrpage.Rmd
never succeeds. It just continues to the next process by knitting the README.Rmd
. As a a result, the badge gets updated signalling that covrpage was completed successfully - but when inspecting the covrpage report ( README ) the file was never updated.
Thanks for the clarification, I'll continue digging.
@yonicd Potential root cause:
# current
covrpage:::package_name("..")
#> Error in normalizePath(path.expand(path), winslash, mustWork) :
#> path[1]="../DESCRIPTION": The system cannot find the file specified
# this works
covrpage:::package_name(".")
See R News about `normalizePath()` - `https://cran.r-project.org/bin/windows/base/NEWS.R-4.0.2.html
inst/_covrpage rmd
is copied into tests
subdir and the rmd is rendered, so the correct input for package_name is ..
, see here for the src script of package_name
nothing in the news notes changed the behavior of normalizpath from what i can see.
you are welcome to use your winOS to see if by forcing a winslash in the normalizePath
call resolves the issue.
this issue may be the stem of the issue https://github.com/r-lib/covr/issues/443 and the reason it is specific to winos runs
https://github.com/r-lib/covr/issues/443 is resolved, but I still can't get this to work (GitHub
version of covr
+ R-devel
), so maybe that wasn't the issue?
This is something that was changed in base R 3.4.6. The dll's arent being released between concurrent sessions in winOS. So when test_dir is run then the package is loaded and coverpage_skip get's locked out from trying to install the package.
I am looking into how to sequence things better with that change in mind.
I can no longer reproduce this issue with 4.1
, so seems to have resolved itself ☺️
I updated to R-devel (
4.0
) and running the following commandis now giving me the following error:
Here is the traceback:
Some other details that might be helpful: