-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Build: fail PDF command (latexmk
) if exit code != 0
#10113
Conversation
We were forcing `exit_code=0` if we detected that `Output written on (.*?)` was found in the standard output of the `latexmk` command. This was producing confusions to our users because the PDF generation failed but we were considering it successful. Now, we are relying on the exit code itself as we do for all the other commands making sure the command succeeded before proceding with the build. Now, if the PDF command fails, we fail the build completely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm +1 with this change. @ericholscher may want to review this as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an obvious and good thing to do, but I do think we'll hear from users on this. It would be really wonderful if we could message this in the build failure smartly, so they know what happened.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for implementing this. I was thinking it wouldn't be too difficult, and I think the UX is much better. I really like this pattern!
Co-authored-by: Eric Holscher <25510+ericholscher@users.noreply.github.com>
We were forcing
exit_code=0
if we detected thatOutput written on (.*?)
was found in the standard output of thelatexmk
command. This was producing confusions to our users because the PDF generation failed but we were considering it successful.Now, we are relying on the exit code itself as we do for all the other commands making sure the command succeeded before proceding with the build. Now, if the PDF command fails, we fail the build completely.
Closes #10015