-
Notifications
You must be signed in to change notification settings - Fork 57
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
Changed Github runner from Conda to Mamba #266
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! @ben-l-p
Codecov Report
@@ Coverage Diff @@
## develop #266 +/- ##
========================================
Coverage 67.69% 67.69%
========================================
Files 166 166
Lines 26709 26709
========================================
Hits 18081 18081
Misses 8628 8628 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Moved all Github runner tests from using Conda to Mamba, a less memory-intensive alternative. Conda was found to require more than the 7gb of RAM available to the Ubuntu runner, causing tests to fail. |
Changed Github runner from Conda to Mamba
The recent change to the new Conda environment involved swapping out minimal environment used by the Github runner to the regular environment. This causes the Ubuntu runner to fail due to running out of its 7GB of RAM, and so new SHARPy versions could not be verified.
To fix this, Conda has been swapped out with Mamba, which is a faster and less memory-intensive drop-in replacement. This should not have any effect on running SHARPy.
Fixed Typos in Linear_Goland_Flutter.ipynb
Small errors in example notebook have been fixed, should not have any effect on the results.