-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Matplotlib 3.9.1 #390
Matplotlib 3.9.1 #390
Conversation
…ForgeAutomergeUpdate
Co-authored-by: jakirkham <[email protected]>
…nda-forge-pinning 2024.06.26.07.13.35
…nda-forge-pinning 2024.06.26.07.13.35
…nda-forge-pinning 2024.06.26.07.13.35
…nda-forge-pinning 2024.06.26.07.13.35
…nda-forge-pinning 2024.06.26.07.13.35
We used cos6 like this for a long time and had no issues so fun! |
Maybe we can use a different mirror source? Looks like UC Irvine maintains one and it goes back quite a bit: https://mirrors.oit.uci.edu/centos/ (though that looks like it is missing something) Alternatively we do the same thing we did with CentOS 6 and switch to the vault mirrors |
Looks like @isuruf started a PR for the latter: conda-forge/docker-images#271 |
We have since deployed a fix Restarting failed CI builds to see if these issues clear up |
Looks like it is passing! 🥳 |
There is already a |
IIUC: There is a |
The rc branch needs to have something like the following in
and then rerender. |
Filed a PR here: #392 |
ah, I was wondering how the 3.9.0 files ended up on the main channel, we must have lost that config while trying to get the builds to work at all. We just did a 3.9.1 so moved this to draft until I get that updated. |
Looks like azure has decided to not run in parallel.... |
@conda-forge-admin please restart ci |
Version 3.9.1 doesn't seem to have made it to the |
Looking at the main branch builds I don't see an entry for this PR's merge: No idea why that would happen. Maybe we could bug the conda-forge folks about this (?) but as a naive attempted solution I'll open a blank PR that someone could merge if they wanted and we could see if that fixes things. |
The interop between github and azure pipelines is fragile; though it works 99+% of the time, there is stuff that breaks, one of them being the case here (no CI started after merge). In this scenario, if you're a regular maintainer, you could do
In case someone from core with access to our azure organisation is around, they can start it manually without that extra commit, which is what I've done now. |
Attempt to merge the rc branch to main.