-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
Remove dev installation of VCPKG #4633
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4633 +/- ##
========================================
Coverage 99.21% 99.21%
========================================
Files 302 302
Lines 22858 22858
========================================
Hits 22679 22679
Misses 179 179 ☔ View full report in Codecov by Sentry. |
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, @kratman! Looks good to me!
PS: I am opening these difficulty: easy
issues for a good-first-issue hackathon at UCL tomorrow (you might have missed this on slack). I would appreciate if they stay open for open-source newbies (most of them are low priority - most development in vcpkg these days is updating mirrors or ports of the packages, so removing the dev installation is not a high priority issue).
I saw that some were being opened for the hackathon, however, this one was related to the IDAKLU separation and I needed to do it in another repo as well |
Ah, I see. Just to be safe, having the dev version of vcpkg should not intervene with the separation in any way (and there is something wrong if it is popping up as a problem in pybammsolvers and not in PyBaMM). |
It is not interfering, I am just trying to keep the wheel builds in sync until I get time to wrap up the last of it |
Description
Removes outdated dev installation of VCPKG during the release
Fixes #4632
Related PR: pybamm-team/pybammsolvers#13
Wheel build: kratman#8
Key checklist:
$ pre-commit run
(or$ nox -s pre-commit
) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)$ python -m pytest
(or$ nox -s tests
)$ python -m pytest --doctest-plus src
(or$ nox -s doctests
)You can run integration tests, unit tests, and doctests together at once, using
$ nox -s quick
.Further checks: