You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While troubleshooting a a failure in a CI/CD pipeline, I found that a covr::codecov call in GitHub Actions broke when I added vetiver as a package dependency. I was very surprised when I was able to replicate this locally; simply removing and restoring vetiver would fix and then break the test.
I couldn't find any references to a known conflict between covr and vetiver and scanning the issues page here I was unable to spot any similar errors. I have zero guesses as to the root cause of this, so any advice would be much appreciated.
Cheers,
Boyd
The text was updated successfully, but these errors were encountered:
While troubleshooting a a failure in a CI/CD pipeline, I found that a
covr::codecov
call in GitHub Actions broke when I addedvetiver
as a package dependency. I was very surprised when I was able to replicate this locally; simply removing and restoringvetiver
would fix and then break the test.I even created a barebones test repo (https://github.com/B0ydT/covr-test) - the full error message is included in the README. With a minimal package and testing structure
covr
works just fine (B0ydT/covr-test@3c9fdc6), but as soon as I add a dependency onvetiver
it fails (B0ydT/covr-test@546ff23).I couldn't find any references to a known conflict between
covr
andvetiver
and scanning the issues page here I was unable to spot any similar errors. I have zero guesses as to the root cause of this, so any advice would be much appreciated.Cheers,
Boyd
The text was updated successfully, but these errors were encountered: