Skip to content

Doc build broken with cryptic message to report this to you (astropy) #3995

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
pllim opened this issue Apr 21, 2018 · 5 comments
Closed

Doc build broken with cryptic message to report this to you (astropy) #3995

pllim opened this issue Apr 21, 2018 · 5 comments
Labels
Support Support question

Comments

@pllim
Copy link
Contributor

pllim commented Apr 21, 2018

Details

Expected Result

Successful build.

Actual Result

Failure with the message, "There was a problem with Read the Docs while building your documentation. Please report this to us with your build id (7074563)."

@pllim pllim changed the title Doc build broken with cryptic message to report this to you Doc build broken with cryptic message to report this to you (astropy) Apr 21, 2018
@stsewd stsewd added the Support Support question label Apr 22, 2018
@adrn
Copy link

adrn commented Apr 23, 2018

I'm seeing the same on a few of my projects, for example:

@RichardLitt
Copy link
Member

Thanks. I'm not able to help with the error message - @humitos should be able to - but I wonder if the message could be improved. Would this be less cryptic?

"There was a problem with Read the Docs while building your documentation. This is most likely a problem with our system, not with you! If you would like to report this, please do so here (https://github.com/rtfd/readthedocs.org/issues/) and use this build ID number: 833292002"

@RichardLitt
Copy link
Member

RichardLitt commented Apr 23, 2018

This is most likely related to #3985.

@agjohnson
Copy link
Contributor

As we learn how to catch more of these errors, the plan is to make these less general. This is a problem with RTD though, so there is no way for a normal user to remedy this, hence the generic error. We'll investigate on our side, but most likely related to bugfix release 2.3.9 and others from last week.

@agjohnson
Copy link
Contributor

Opened #3999 to deal with this, I'm rolling all the reports up there.

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

5 participants