Skip to content
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

[Feat] Imrove error verbosity during d2lbook build pdf #49

Open
AnirudhDagar opened this issue Mar 31, 2022 · 1 comment
Open

[Feat] Imrove error verbosity during d2lbook build pdf #49

AnirudhDagar opened this issue Mar 31, 2022 · 1 comment
Assignees

Comments

@AnirudhDagar
Copy link
Member

Currently, CI errors out with exit code 255 in case of Latex syntax errors and doesn't show the exact errors on the CI log.

Latexmk: Summary of warnings:
  Latex failed to resolve 92 reference(s)
  Latex failed to resolve 38 citation(s)
Collected error summary (may duplicate other messages):
  pdflatex: Command for 'pdflatex' gave return code 256
Latexmk: Use the -f option to force complete processing,
 unless error was exceeding maximum runs of latex/pdflatex.
Latexmk: Errors, so I did not complete making targets
Makefile:29: recipe for target 'd2l-pt.pdf' failed
make: *** [d2l-pt.pdf] Error 12
script returned exit code 255

One example where this could have been useful is attached here.

This is then handled only by running d2lbook build pdf locally to reproduce the issue and fix the latex errors, which is frustrating and quite inconvenient.

The proposed feature request is for improved logging of these latex errors to facilitate easier and transparent debugging using CI Logs.

cc @astonzhang

@AnirudhDagar AnirudhDagar self-assigned this Mar 31, 2022
@astonzhang
Copy link
Member

Indeed, a nice feature to have -- so no need to debug latex locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants