TST: replace pip with uv in CI #5311
Draft
+66
−75
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
neutrinoceros
added
tests: running tests
neutrinoceros
force-pushed
the
tst/locked-ci
branch
from
caed110 to
68c756a
Compare
|
bleeding-edge failures are unrelated, see yt-project/unyt#599 |
neutrinoceros
force-pushed
the
tst/locked-ci
branch
4 times, most recently
from
880ff21 to
6e69af1
Compare
neutrinoceros
force-pushed
the
tst/locked-ci
branch
from
b073b25 to
eff6b4a
Compare
|
I'm struggling to adapt the sdist test. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
This is the first step towards #5310. I'm not adding a lock file yet, but I'm migrating existing CI to use uv instead of pip. From there, adding the lockfile will be a formality.
PR Checklist