Skip to content

Build log says "failed" but logs say PDF file successfully created #1065

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
gerv opened this issue Dec 4, 2014 · 6 comments
Closed

Build log says "failed" but logs say PDF file successfully created #1065

gerv opened this issue Dec 4, 2014 · 6 comments
Labels
Bug A bug

Comments

@gerv
Copy link

gerv commented Dec 4, 2014

We are getting (PDF) builds marked as failed, but the build log seems to suggest that the PDF was successfully created.

https://readthedocs.org/builds/bugzilla/1921250/

This finishes with:
Output written on Bugzilla.pdf (180 pages, 626340 bytes).
but still the build page:
https://readthedocs.org/builds/bugzilla/
lists the build as failed. :-(

Issue #979 may be related.

Gerv

@gerv
Copy link
Author

gerv commented Dec 10, 2014

This may be to do with the errors thrown in the middle of the build:

l.11410 ...dєr Séçretíøns\PYGZdq{}}\PYG{p}{,}

! Package inputenc Error: Unicode char \u8:ї not set up for use with LaTeX.

I solved this on my local Ubuntu box by installing the texlive-lang-cyrillic package...

Gerv

@hwine
Copy link

hwine commented Jan 16, 2015

Gerv - I have a similar issue (different character) for the releng PDF -- how did you fix the issue for the hosted version?
Hal

@gerv
Copy link
Author

gerv commented Jan 16, 2015

I believe we solved it by removing the character from the PDF :-| It was only in an example, so it was easy to change. Sorry not to give a more useful answer.

@gregmuellegger
Copy link
Contributor

@hwine is this still an issue for you?

@gregmuellegger gregmuellegger added the Needed: more information A reply from issue author is required label Jul 20, 2015
@hwine
Copy link

hwine commented Jul 23, 2015

It would be great if alternate character sets were supported, but sufficient if PDF failures are at least reported. At the time I commented, I thought I also opened an issue about non-html formatting failures, but I can't find that at the moment.

Like @gerv, I also modified my source to remove the unsupported characters.

Thanks for checking!

@gregmuellegger gregmuellegger added Bug A bug and removed Needed: more information A reply from issue author is required labels Jul 24, 2015
@ericholscher
Copy link
Member

This is now fixed with #1524 :)

@readthedocs readthedocs deleted a comment from vonhatduc Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug
Projects
None yet
Development

No branches or pull requests

4 participants