Skip to content

Build ends with Unknown Error (html is generated but no PDF) #3277

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
piogor opened this issue Nov 16, 2017 · 6 comments
Closed

Build ends with Unknown Error (html is generated but no PDF) #3277

piogor opened this issue Nov 16, 2017 · 6 comments
Labels
Support Support question

Comments

@piogor
Copy link

piogor commented Nov 16, 2017

Details

Expected Result

Build all documentation (html, PDF) without failing or meaningful error description ;-).

Actual Result

Build ends with the following error:

Error

Unknown error encountered. Please include the build id (6278204) in any bug reports

However html was built but no new PDF output was generated (there is still old version available for download).

@piogor
Copy link
Author

piogor commented Nov 16, 2017

Again, I have investigated problem on my local environment - for some reason Sphinx 1.5.6 starts to generate corrupted latex output:

tango-controls/tango-doc#137

It is enough to require Sphinx>=1.6.5 to solve the issue.

Anyway, it would be nice to have a way of getting access to more info about problematic builds (like pdflatex terminal output).

@piogor piogor closed this as completed Nov 16, 2017
@RichardLitt
Copy link
Member

@piogor your suggestion for more information might get lost. A targeted issue asking for more info about problematic builds, in the case of pdflatex specifically, might be a good one to open.

Thanks for taking the time to log your problem and solution!

@piogor
Copy link
Author

piogor commented Nov 16, 2017

I will open the issue :).

@agjohnson
Copy link
Contributor

This is an unhelpful error because something happened at the system level and we didn't catch the error. Raising a traceback is a security hole, so we're moving from "Oops, oh well" messaging to "Oops, well here's a reference" instead.

We'll address the particular issue here and hopefully come up with an actual error that we can catch for this case.

@agjohnson agjohnson added the Support Support question label Nov 16, 2017
@agjohnson agjohnson added this to the Build error reporting milestone Nov 16, 2017
@RichardLitt
Copy link
Member

Thanks for explaining, @agjohnson. Sounds good.

@stsewd
Copy link
Member

stsewd commented Nov 28, 2018

I'm closing this issue in favor of #4288, which is about the problem why the output of pdflatex wasn't shown.

@stsewd stsewd closed this as completed Nov 28, 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

4 participants