You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current mechanism for determining the exit code at the end of compilation is based on the final compilation output, which is a pair of strings corresponding to the stdout and stderr output. If the final stderr output starts with ###, which is printed at the beginning of error messages, the compiler will have a non-zero exit code. (See condition and its application). Most failures in the compilation stages cause such an error message. Separately to this, all current success cases provide non-empty stdout output and all current failure cases provide empty stdout output.
In general, it would be nice if this mechanism was not so dependent on this specific prefix, and the final compilation output was more explicit about which exit code applied.
The text was updated successfully, but these errors were encountered:
The current mechanism for determining the exit code at the end of compilation is based on the final compilation output, which is a pair of strings corresponding to the
stdout
andstderr
output. If the finalstderr
output starts with###
, which is printed at the beginning of error messages, the compiler will have a non-zero exit code. (See condition and its application). Most failures in the compilation stages cause such an error message. Separately to this, all current success cases provide non-emptystdout
output and all current failure cases provide emptystdout
output.In general, it would be nice if this mechanism was not so dependent on this specific prefix, and the final compilation output was more explicit about which exit code applied.
The text was updated successfully, but these errors were encountered: