Skip to content

Build timeout #3360

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

Closed
cdeil opened this issue Dec 5, 2017 · 2 comments
Closed

Build timeout #3360

cdeil opened this issue Dec 5, 2017 · 2 comments
Labels
Support Support question

Comments

@cdeil
Copy link

cdeil commented Dec 5, 2017

Details

Expected Result

Build passed

Actual Result

Build timeout.


Would it be possible to surface the build log from the step that times out?

I suspect it's the HTML sphinx build, but I'm not sure.

For the build steps you do show, they are together < 5 min and the last one is this one and succeeds:

cat docs/conf.py

Locally the HTML sphinx build takes 5 min on my machine, so I'm surprised that our build times out here!?

If the HTML build time really is the issue, would it be possible to increase the docs build time for this project a bit?

I promise to try and reduce it by doing a bit less in our Sphinx build and limit the number of commits to master that will trigger a build on RTD. I can also try to get some funding, but this will not happen immediately, and in the meantime I can't do a release because our docs and changelog are outdated.

@RichardLitt RichardLitt added the Support Support question label Dec 7, 2017
@cdeil
Copy link
Author

cdeil commented Jan 9, 2018

We've decided to move Gammapy away from RTD (work in progress: gammapy/gammapy#1241). Either build on travis-ci or our Jenkins, and host on gh-pages.

RTD maintainers: Thank you very much for setting up and supporting this great service!!! It was of great help to our project over the past years, and for me still is for several other Python package docs I have.

If someone has a link with information how to do the multi-version cross-linking of the docs like RTD does it, outside of RTD, please leave a comment!

Also, if there's some link with information how to extract or archive existing docs from RTD on check-out (e.g. a zip file or tarball with the HTML docs from past version that are being served), please leave a comment!

@RichardLitt
Copy link
Member

Thank you for letting us know, @cdeil, for the nice words, and for clearly saying what you would need to come back!

@agjohnson do we have issues that you know of for those two requests he mentions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Support Support question
Projects
None yet
Development

No branches or pull requests

2 participants