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

emit precompile statements to separate file #28419

Merged
merged 1 commit into from
Aug 3, 2018

Conversation

KristofferC
Copy link
Member

@KristofferC KristofferC commented Aug 3, 2018

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.

if the filename to trace--compile is stdout, print to the stdout stream
@KristofferC KristofferC force-pushed the kc/emit_file_precompile branch from f3edd02 to d1be419 Compare August 3, 2018 00:19
@KristofferC KristofferC merged commit cfc7475 into master Aug 3, 2018
@KristofferC KristofferC deleted the kc/emit_file_precompile branch August 3, 2018 08:56
ararslan pushed a commit that referenced this pull request Aug 3, 2018
if the filename to trace--compile is stdout, print to the stdout stream
(cherry picked from commit cfc7475)
KristofferC added a commit that referenced this pull request Feb 11, 2019
if the filename to trace--compile is stdout, print to the stdout stream
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

Successfully merging this pull request may close these issues.

3 participants