Documentation builds take too long and sometimes die
See original GitHub issuehttps://readthedocs.org/projects/poliastro/builds/12697560/
Command killed due to excessive memory consumption
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
How long is too long for a build? - Industrial Logic
When the build slows beyond certain thresholds, there are predictable responses by a team that lead to slower builds, lower code quality, and ......
Read more >There was a problem with Read the Docs while building your ...
We have been experiencing a potentially similar failure for several weeks: Project: https://readthedocs.org/projects/indra/; Failing build url: ...
Read more >Common Build Problems - Travis CI Docs
Our builds have a global timeout and a timeout that's based on the output. If no output is received from a build for...
Read more >Commit Virtual 2021: Documentation is Dead, Long Live ...
Speaker: Benedikt Stemmildt, Philipp WestphalenDocumentation is important—in companies of all sizes—but developer want to write code, ...
Read more >Why does it take so long to build software? - Simple Thread
Why does it take so long to build software? We hear variations of this question frequently: Why is building software so expensive?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Looks like lots of RAM is needed to build our docs from scratch (~3 GB are not enough). RTD increased the capacity of our builders. The issue is closed!
Grr
masterbuilds keep failing but pull request builds keep passing. We’ll have to wait for RTD folks to lend us a hand.