-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Use Mamba in Azure CI #45902
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
Use Mamba in Azure CI #45902
Conversation
5c6d2e0
to
cc790fe
Compare
cc790fe
to
edaa438
Compare
edaa438
to
53da160
Compare
ping @mroeschke |
Did mamba solve unpinned dependencies differently than conda for builds in Azure? For example in GHA builds, I noticed mamba would install pyarrow=2 while conda would install pyarrow=6 |
It seems like it always installs Arrow 6, so no change in version. Edit: Ran a diff of all versions, no changes except for build numbers which are due to different start times I am assuming. |
b2dc629
to
ffd4433
Compare
499d6a9
to
3c5bb13
Compare
@jonashaag please don't force push after an approval. |
@simonjayhawkins Thanks, will keep that in mind in the future. In this case it was a rebase to latest |
Hmm, seems like there is a problem with Azure and Mamba, see mamba-org/mamba#488
|
Is this a full blocker for implementing this? |
Let's try the workaround suggested there. |
This seems to fix the issue, although I'm not sure if will reappear. The other repos that have this implemented successfully for some time indicate that it's not the case but I don't feel confident about that. |
thanks @jonashaag very nice! |
@meeseeksdev backport 1.4.x |
Something went wrong ... Please have a look at my logs. |
Co-authored-by: Jonas Haag <[email protected]>
Use Mamba in Azure CI to save ~10 minutes of setup time.
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.