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

Print build/doc/*.log to console in case of error #254

Open
yegor256 opened this issue Oct 29, 2022 · 5 comments
Open

Print build/doc/*.log to console in case of error #254

yegor256 opened this issue Oct 29, 2022 · 5 comments

Comments

@yegor256
Copy link
Contributor

Now, if l3build doc fails, it prints this:

Transcript written on debate.log.
Typesetting debate
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022) (preloaded format=pdflatex)
 \write18 enabled.
entering extended mode
 ! Compilation failed

Would be great to see the full content of build/doc/*.log. Now I have to manually check it after each build failure.

@FrankMittelbach
Copy link
Member

or rerun with halt on first error in that case?

I'm not sure that showing the full log(s) in that case it helpful because they tend to be long and could be many, but maybe it would be nicer if (just like with the tests) a listing of the failed files is shown.

@zauguin
Copy link
Member

zauguin commented Oct 29, 2022

There already is --show-log-on-error. It doesn't print all logs but only the logs from failed runs (which is typically what you want)

@FrankMittelbach
Copy link
Member

looks like I haven't been keeping up with what got added as command line options :-)

@yegor256
Copy link
Contributor Author

@zauguin this option doesn't really help, please see this log: https://github.com/yegor256/ffcode/actions/runs/3354309446/jobs/5557767038

@yegor256 yegor256 reopened this Oct 30, 2022
@zauguin
Copy link
Member

zauguin commented Oct 30, 2022

Sorry, I missed that you were talking about building the docs and not the tests.

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

3 participants