I debugged and found the issue with Ubuntu on Github Actions. The installer action was causing the Rprovider test project to build infinitely, as R.NET was hanging on the creation of an engine instance. Normal Ubuntu package installs work fine - tested locally and on WSL with R 3.5 and 4.1. Changed the github actions to use a standard install procedure for R rather than the r action - addresses #238
Types of changes
What types of changes does your code introduce to RProvider?
Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[x] Build and tests pass locally
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Proposed Changes
I debugged and found the issue with Ubuntu on Github Actions. The installer action was causing the Rprovider test project to build infinitely, as R.NET was hanging on the creation of an engine instance. Normal Ubuntu package installs work fine - tested locally and on WSL with R 3.5 and 4.1. Changed the github actions to use a standard install procedure for R rather than the r action - addresses #238
Types of changes
What types of changes does your code introduce to RProvider? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...