-
Notifications
You must be signed in to change notification settings - Fork 75
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
petsc rerender error #2561
Comments
How long does the local rerender take? I wonder if the timeout is the issue. The bot kills the job at 900 seconds. |
timeout makes sense, it takes 600 seconds on my m1 mac. |
petsc suitesparse migration rerender succeeded after failing for a while, and it looks like it took 630 seconds. mumps also unstuck, so not sure if there's still an action to take here? It could be really useful if there were a way to manually issue PRs that the migrator recognizes as part of the migration when the migrator fails. |
Yes, or we could have the bot just issue the PR and make a rerender comment in the PR. I don't want to do that in general so that we don't overload GHA, but it might be ok here. |
FWIW, this is happening again in petsc4py, which currently has 260(!) variants and takes over half an hour on my machine to rerender (it takes less time to build all variants in parallel on CI than to rerender with no changes). Unfortunately, ~all of the time is in petsc4py variants have 5 dimensions now:
so each linux target has 72 variants to render. Surprisingly (to me, at least), profiling with pyinstrument suggests that it spends a huge fraction (80% of render_recipe) in Rendering just 24 variants results in 24 calls to So if copying metadata for variants can be optimized, I think overall a massive amount of rerender time can be saved across conda-forge. |
Yep. See this PR: conda/conda-build#5281 We should get that in. |
Nice! That should help. On investigation, I doubt conda/conda-build#5281 reduces petsc4py rerender from over 30 minutes to under 5. The next limiting factor is in |
Yes and this function has other odd side effects which make conda-build hard to use. We should open an issue. |
With the optimized PRs and conda-forge/conda-smithy#1967 petsc4py renders in under 5 minutes. The next limiting factor is in the calls to |
rerenders of petsc have started to fail, I believe starting with the merge of conda-forge/petsc-feedstock#193, which adds cuda builds.
The bot error doesn't show any actual errors and a manual rerender with the migrator succeeds, so I suspect it could be a memory exhaustion issue.
bot error
The text was updated successfully, but these errors were encountered: