-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Build time out when hitting the api to get active versions #6304
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
any update? we're continuing to see a lot of transient failures, especially when multiple builds in the same project are run simultaneously |
It may be related to time outs, I'll increase the build time of the projects on monday |
thanks for your help! |
@stsewd were you able to increase the build time yesterday? the failures have become more consistent now, but the error message simply says "There was a problem with Read the Docs while building your documentation. Please try again later. However, if this problem persists, please report this to us with your build id" |
Sorry, I wasn't able to get to this yesterday, I'm checking now. |
Looking at this doesn't look like it's from timeout. Not sure what's causing it. I'm investigating a little more |
I wasn't able to reproduce this locally, but I found this in the logs
|
hmm was there anything around that line that might suggest what could be causing the 502 response? |
I'm investigating that. It's probably a slow query. |
Looks like the slowness is because the amount of active versions your project has (149). I'm seeing the same on projects that have more than 100 active versions. This number of project with more than 100 active versions is really low, though. There are only 7 projects affected by this. The explanation, we are hitting azure cloud storage to check if the epub, zip, pdf files exists readthedocs.org/readthedocs/projects/models.py Lines 779 to 791 in d298ff5
The API returns that here
(but we actually don't use that value for building) Anyway, we are in the progress of a solution to avoid querying azure that much #6278 In the mean time, if you don't really need to keep all 149 versions active, you can disable them https://readthedocs.org/projects/sagemaker/versions/. Having less than 100 active versions should make the builds happy again. |
Great, thanks for digging into this! I see #6278 has been merged - is there an ETA on when that will be released? |
@laurenyu the above PR is just one part of what needs to be done to reduce the number of queries. |
We now don't query azure anymore readthedocs.org/readthedocs/builds/models.py Lines 375 to 399 in ae6aeb5
|
Uh oh!
There was an error while loading. Please reload this page.
Details:
Expected Result
Build succeed
Actual Result
Based on the build history, the builds have been failing and passing inconsistently.
The following things are inconsistent when looking at our build history:
Can we get some insight into why the builds failed, specifically for these:
The peculiar thing is that this next build succeeded but it was a one line change in the code, with not much changes in the RST or documentation.
Corresponding changes for the build above:
The text was updated successfully, but these errors were encountered: