Skip to content
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

MNT: rerender #120

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I've started rerendering the recipe as instructed in #119.

If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!

Here's a checklist to do before merging.

  • Bump the build number if needed.

Fixes #119

@conda-forge-webservices
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@h-vetinari
Copy link
Member

@conda-forge-admin, please rerender

@beckermr
Copy link
Member

@conda-forge-admin rerender

trying again since this used the old conda-build even though the docker image was rebuilt...

@h-vetinari
Copy link
Member

since this used the old conda-build

The new builds are only just now starting to make their way through the CDN. Windows builds just became visible, linux-64 should be in 10-15min.

@h-vetinari
Copy link
Member

@beckermr, do you need to verify something specific with the CI run here? I'd like to cancel it as it's pointlessly wasting resources.

@beckermr
Copy link
Member

I am checking timing with the new conda build. Feel free to cancel.

@beckermr
Copy link
Member

yeah CDN delay here was ~1 hour from when the build hit anaconda.org to when it was in the repodata. That is a lot slower than usual.

cc @conda-forge/core

@beckermr
Copy link
Member

@conda-forge-admin rerender

@beckermr
Copy link
Member

7 minutes - not bad! 2x faster!

@h-vetinari
Copy link
Member

yeah CDN delay here was ~1 hour from when the build hit anaconda.org to when it was in the repodata. That is a lot slower than usual.

Nah, 2-3h is standard these days (especially across all architectures; individual arches are available sooner depending where in the cyclic(?) schedule of subdir-updates we land), and can be up to 5h if a file clone fails and needs to be retried, see conda/infrastructure#892

@h-vetinari
Copy link
Member

7 minutes - not bad! 2x faster!

Awesome work @mbargull @kenodegard et al.! 💪 🙏

@beckermr
Copy link
Member

Oh really? It was like 10 minutes just a few years back. What happened?!

@beckermr
Copy link
Member

Ugh that's not a fun read.

@jakirkham
Copy link
Member

If you have ideas on additional statistics that we can share, please feel free to add them here: conda/infrastructure#935 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

@conda-forge-admin, rerender
4 participants