Skip to content

Builds timing out in the build phase, but no logs available from that phase #3213

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
juanrubio opened this issue Oct 31, 2017 · 5 comments
Closed
Labels
Needed: more information A reply from issue author is required Support Support question

Comments

@juanrubio
Copy link

Details

Expected Result

Builds are being killed after 900 seconds and I would expect the logs from the execution up to that point to be available for inspection.

Actual Result

The build is killed in the build stage, and the logs from that stage are not available. The last stage that have its logs available is

cat docs/sphinx-src/conf.py

A few notes:

  • My project uses breathe and doxygen to produce embedded C API info.
  • The build process, i.e. doxygen xml + sphinx generation takes in my PC around 45 seconds.
  • The last successful RTD build took 335 seconds and was this one here:
    https://readthedocs.org/projects/tizonia-openmax-il/builds/5919677/
  • No major sphinx configuration changes since the last successful build. Changes in the C/C++ code base only (a couple of extra thousand lines code).
@juanrubio
Copy link
Author

I've noticed #3122.

I'm rebuilding without PDF to see if that fixes the timeout issue.

@juanrubio
Copy link
Author

OK, so that new build (no PDF) still has failed in the build phase, but this time, the logs from that phase have showed up in the site:
https://readthedocs.org/projects/tizonia-openmax-il/builds/6202844/

building [readthedocs]: targets for 59 source files that are out of date
updating environment: 61 added, 0 changed, 0 removed
reading sources... [  1%] development/BUILDING
reading sources... [  3%] development/clients/clients
reading sources... [  4%] development/clients/libtizdirble
reading sources... [  6%] development/clients/libtizgmusic
reading sources... [  8%] development/clients/libtizsoundcloud
reading sources... [  9%] development/clients/libtizyoutube
Killed

Any idea on why the build stage takes 588 seconds while on my pc it's less than 50?. Anything that I can do on my side to speed this up?

@RichardLitt RichardLitt added the Support Support question label Oct 31, 2017
@stsewd
Copy link
Member

stsewd commented Aug 31, 2018

For the command not showing I opened #4288.

We migrate to Azure recently, we have faster builders now, could you test if your project is still falling?

@stsewd stsewd added the Needed: more information A reply from issue author is required label Aug 31, 2018
@stsewd
Copy link
Member

stsewd commented Sep 18, 2018

Closing this as the user hasn't responded or given more information, feel free to reopen with more information if you are still having this problem :).

Also, you can check https://docs.readthedocs.io/en/latest/guides/build-using-too-many-resources.html

@stsewd stsewd closed this as completed Sep 18, 2018
@juanrubio
Copy link
Author

Sorry, I forgot to report back!. Yes, builds are faster now. My builds are now completing in under 50 seconds. Thanks!.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: more information A reply from issue author is required Support Support question
Projects
None yet
Development

No branches or pull requests

3 participants