emit precompile statements to separate file #28419
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Emitting precompile statements directly to stdout is a bit brittle when other things also can print to there. This can cause failures when precompile statements gets interleaved with other stderr output (e.g. CI failure here https://build.julialang.org/#/builders/93/builds/526).
Instead, emit these statements to a separate file by setting
--trace-compile=file
. For convenience,--trace-compile=stderr
still prints to stderr since it can be a useful inspection tool.Good to look at diff with whitespace turned off because a
mktemp
changed an indentation.Thanks to @Keno for help.