-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Builds use a smaller builder when moving from pip to conda #8004
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
Comments
Hi, looks like both builds are using the same build (big builders). Looks like this is due to an error on the build rather than a memory issue.
|
@stsewd Are you looking at https://readthedocs.org/projects/dirac/builds/13216630/? If so that was intentionally a test to bypass the logic I linked above and shorten the the amount of time the build would take. I'm fairly sure the build I linked in the original post (https://readthedocs.org/projects/dirac/builds/13209708/) must have ran on a small builder as it failed with "Command killed due to excessive memory consumption". |
Hmm, yeah, that one run on a smaller builder. Not sure how I ended up in the other build.
the docs already mention to contact us to increase resources in case of problems. So, the problem is with our task router, yeah. We could move the conda check before doing the external version check. /cc @humitos. |
This is an edge case and I'm not sure how to solve it. We use historical builds data to know which would be the best queue to build the current build. At this point we don't have the I think we should mark this project to use
|
Details
We decided to try enabling the
conda
for the build environment for our docs so we could avoid mocking dependencies and remove the duplication between the tests and docs setup. I developed this by making a new project on readthedocs to build documentation using my fork and then opened a PR to the main repository. Surprisingly the builds now always fail with memory errors or timeouts.It seems like the small build nodes are being used instead of the larger conda compatible ones. I've done some digging and it seems like #7912/#7933 added a feature to "lock" external builds to the queue used for the latest build:
readthedocs.org/readthedocs/builds/tasks.py
Lines 85 to 104 in 7450d6d
I'm not sure how easy this is to fix. If it's difficult perhaps the easiest solution is to document this quirk in the conda troubleshooting section. I'm happy to make a PR for the docs if that's the way you want to go.
Expected Result
Builds in a copied repository work the same as in the original one.
Actual Result
Moving to the upstream repository caused builds to fail.
The text was updated successfully, but these errors were encountered: