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
During our Legion build we also do the build of the legion profiler (which goes through Corrosion), and that happens in a recursive invocation of cmake:
[0/227] cd /home/mpapadakis/condagcc/legion/tools/legion_prof_rs && /home/mpapadakis/condagcc/env/bin/cmake -E env ...
At that point the sub-cmake seems to take over the output, and prints out successive lines of which package it’s compiling, e.g.
I tried disabling cargo's progress bar CARGO_TERM_PROGRESS_WHEN=never, but that didn't help.
I'm reporting this here because I was not able to reproduce using a pure Legion build, so it possibly has something to do with the recursive build of Legion that we do during legate.core build, or possibly our use of ninja, or who knows what.
manopapad
changed the title
Build output from the Rust Legion profiler hides output of concurrent C++ builds
Output from Rust profiler build hides concurrent C++ build output
Oct 13, 2023
During our Legion build we also do the build of the legion profiler (which goes through Corrosion), and that happens in a recursive invocation of cmake:
At that point the sub-cmake seems to take over the output, and prints out successive lines of which package it’s compiling, e.g.
In the meantime, other targets from the parent cmake invocation continue to be built, but their output is lost.
See no-corrosion.txt and with-corrosion.txt for a comparison.
I tried disabling cargo's progress bar
CARGO_TERM_PROGRESS_WHEN=never
, but that didn't help.I'm reporting this here because I was not able to reproduce using a pure Legion build, so it possibly has something to do with the recursive build of Legion that we do during legate.core build, or possibly our use of ninja, or who knows what.
On a pure Legion build:
I see the lines from corrosion/cargo mixed together with the C++ compilation lines, but at least no lines get lost.
The text was updated successfully, but these errors were encountered: