Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Circle: Build docs in parallel.#20718
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Looks like the build ran out of memory? |
QuLogic commentedAug 4, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
On recent Circle builds, I noticed it said we have access to a higher resource class, so I bumped it up to |
This doubles the vCPU and RAM, which will hopefully be enough to run inparallel.
We are now on large Docker VMs, which offer 4 vCPUs, so we should try tobuild in parallel.
Re-reading the resource class docs again, it looks like the system really has 32 cores, and since I passed But we might as well save the 5 minutes by going to |
PR Summary
We are supposedly on medium Docker VMs, which offer 2 vCPUs, so we should try to build in parallel.
PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
and runflake8 --docstring-convention=all
).doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).