-
Notifications
You must be signed in to change notification settings - Fork 278
Experiment with caching conda environment in Azure #1495
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
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1495 +/- ##
=======================================
Coverage 86.20% 86.20%
=======================================
Files 396 396
Lines 50341 50341
Branches 5311 5311
=======================================
Hits 43396 43396
Misses 5492 5492
Partials 1453 1453 ☔ View full report in Codecov by Sentry. |
You’ll need to explicitly pin the version of everything in the CI environment to make this correct. |
Right. I think what I want to achieve is to create a single environment within each run. In that case I need to create an artifact instead of caching the environment. |
Summary
Experiment with caching the conda environment we need to create in Azure to
run simpeg tests. This way we could reduce the runtime of CI by reusing the
created environment.
PR Checklist
expect style.
to a Pull Request
@simpeg/simpeg-developers
when ready for review.Reference issue
What does this implement/fix?
Additional information