-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Improve part of the output of --toolchain_resolution_debug
#26037
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
base: master
Are you sure you want to change the base?
Conversation
52f3180
to
61d1bac
Compare
@katre @gregestren Please let me know what you think of the new output format. If you like it, I will update the tests. |
--toolchain_resolution_debug
--toolchain_resolution_debug
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add an example output with these changes?
/** Report on which toolchains were selected. */ | ||
void reportSelectedToolchains( | ||
void startDebugging( | ||
EventHandler eventHandler, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the eventHandler
ultimately comes from the SkyFunction.Environment
, why not save it during the create
call? Why pass it to every method? Are the instances changing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, there is a check in Skyframe that specifically guards against this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let me know when the tests are fixed, and please add an example of the new output to the description.
This improves the debug output of
ToolchainResolutionFunction
(but notSingleToolchainResolutionFunction
) in several ways:A preexisting problem that hasn't been fixed is that messages about rejected or removed execution platforms is interleaved with other output and thus can't easily be linked to the start/finish messages. How to resolve this in the context of Skyframe restarts and messages printed by the "child" SkyFunction
SingleToolchainResolutionFunction
remains an open problem.Work towards #11984