-
Notifications
You must be signed in to change notification settings - Fork 62
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
Output from Rust profiler build hides concurrent C++ build output #860
Labels
bug
Something isn't working
Comments
I tried passing
This kills all the output from the
|
manopapad
pushed a commit
that referenced
this issue
Mar 5, 2025
* build-system::python-requires is a full version spec, so specify that any python >=3.10 works for us
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: