Testthat error in test-coverage workflow

[pakjiddat]

The covr::codecov() calls gives the following error:

See attached log file.
logs_103.zip

As I understand covr::codecov() runs all the test cases using testthat. The error message suggests there is a problem with running the testthat test cases.

I checked the test cases in my package and the problem seems to be caused by the following function call:

sfp <- system.file("extdata", fn, package = "wordpredictor")

The file name given by fn cannot be found. The function returns an empty string. The command: covr::codecov() works on my local computer without problems.

I replaced the command covr:codecov() with covr::codecov(quiet = F, clean = F, type = "all") in test-coverage.yaml. It should run all tests, examples and vignettes. Running the workflow resulted in the following error:

> tools::buildVignettes(dir = '/Users/runner/work/word-predictor/word-predictor')
--- re-building ‘features.Rmd’ using rmarkdown
Quitting from lines 63-82 (features.Rmd) 
Error: Error: processing vignette 'features.Rmd' failed with diagnostics:
no file found
--- failed re-building ‘features.Rmd’

See the attached log file.
logs_107.zip

The error suggests a problem with file/folder permissions.

[jimhester]

As mentioned in #319 (comment) your vignettes are broken.

If you continue to have issues along this line please open them at community.rstudio.com, this issue tracker is only for issues in the custom actions themselves, not general help with debugging workflows.

[pakjiddat]

I managed to fix the problem. The problem was related to #319. I had added inst/extdata folder to .gitignore. So the files were not added to the GitHub repo. I removed the inst/extdata entry from .gitignore and committed the changes. After that the test-coverage workflow ran without problems. Thanks for your help !.

I had posted this issue with the check-release workflow at community.rstudio.com, three days ago. But have not yet received a reply.

[github-actions]

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