Skip to content

Installation timeout #4691

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
rsyi opened this issue Oct 1, 2018 · 4 comments
Closed

Installation timeout #4691

rsyi opened this issue Oct 1, 2018 · 4 comments
Labels
Support Support question

Comments

@rsyi
Copy link

rsyi commented Oct 1, 2018

Details

Installation times out before docs can be built. Not sure if this is a common problem -- is there anything I can do to allow the build to occur more quickly? I tried disabling the epub and pdf compilations, but it doesn't quite help. It appears the installation fails during the python install step.

Expected Result

Docs build normally.

Actual Result

Installation times out, docs not built.

@stsewd
Copy link
Member

stsewd commented Oct 1, 2018

The command that fails isn't that one (#4288), so probably is failing when installing your requirements or building the actual html.

Did you read this https://docs.readthedocs.io/en/latest/guides/build-using-too-many-resources.html?

If that doesn't help, I'll investigate a little more. Also, you can request more time/memory is nothing else helps.

@stsewd stsewd added the Support Support question label Oct 1, 2018
@rsyi
Copy link
Author

rsyi commented Oct 1, 2018

Ah no I didn't see that page yet. I have functioning documentation now, thank you!

For those who come across a similar problem, here were my steps towards resolution:

  • I added a readthedocs.yml file that set formats: [] and python: use_system_site_packages: true and found that the build now gave me more informative error messages: https://readthedocs.org/projects/pylift/builds/7874640/
    For some reason, it seems that the requirements.txt file I had by default in my parent directory was being used!
  • Add in a rtd_reqs.txt file (empty), and explicitly specify that as my requirements file in the Advanced Settings section.

Does this mean by default the requirements.txt file I had in my parent directory was being used by readthedocs?

@stsewd
Copy link
Member

stsewd commented Oct 1, 2018

Does this mean by default the requirements.txt file I had in my parent directory was being used by readthedocs?

Yes, rtd by default tries to install a requirements.txt file, you'll be able to skip that in our v2 of the config file #1621 (comment), for now using a empty file is a workaround.

Can we close this issue?

@rsyi
Copy link
Author

rsyi commented Oct 1, 2018

Great good to know. Thanks, and yes!

@rsyi rsyi closed this as completed Oct 1, 2018
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