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
Interrupt documentation build on error #15455
Comments
Branch: u/vbraun/docbuild_error |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
Changed author from Volker Braun to none |
Reviewer: Jeroen Demeyer |
comment:6
Isn't this already happening? |
comment:8
No, concurrent workers are not interrupted. Especially PDF build errors are typically sandwiched between 1000's of lines of unrelated output. |
comment:9
I'm not sure I would want concurrent workers interrupted, at least for html docs. If This might be more useful for the PDF docs, since I don't think the docbuilder does a good job of detecting whether the docs have been successfully built already. |
comment:10
Of course the annoyance factor depends on how much the concurrent jobs spew out. In a makefile, gcc will only add a line or so which is negligible. But you really want to see the error within the last ~50 lines, everything else is imho very confusing. The thousands of lines of PDF output easily flood the scrollback buffer, that I'd call a total disaster. |
comment:11
Fortunately, the PDF build is logged. If the PDF build fails, maybe we could get better error-reporting: report, for example, if there is a (recent?) LaTeX file in Comparing with |
comment:12
Its a recurring pain point that people fail to find the errors in their PDF file, but I guess it just hurts to be stupid. |
comment:14
Huh? I thought you disagreed with closing this? |
Interrupt documentation building if an error is encountered. Aso, search output for more error conditions (equivalent to Jeroen's release manager script).
Component: documentation
Branch/Commit: u/vbraun/docbuild_error @
f6accfa
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/15455
The text was updated successfully, but these errors were encountered: