-
Notifications
You must be signed in to change notification settings - Fork 467
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
Add tooling to explain why a graph execution happens #5723
Conversation
<< "======================================================================" | ||
"==========" | ||
<< "\n"; | ||
if (frames[0].function == "mark_step") { |
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.
Wondering if it worths logging frames[0].function;
for the cases other than mark_step
.
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.
yea I want to expand this a bit later to cover most of the common cases of the execution.
I need to add some test, will try to do that this week |
f897811
to
6dd0623
Compare
This should be ready for review. |
I will update troubleshotting in a separate pr. |
@will-cromar Can I get a review for this one? |
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.
I think this information is already in the dumped graphs?
Will the UX be better with this change where the information is printed to the console? It may not be the case as the information will be interleaved with the user code.
dumped graph is in a separate file and it always dump the HLO or IR which can be huge. The idea is that we should dump something more concise and provide some explanation on what is happening, this can be interleave with the debugging message user added to their model code. |
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.
@carmocca FYI, this is a WIP I will add more to this tooling. |
* Initial commit for debugging tool * minor format tweak * Only master process should print the execution frame info * add execution cause * handle dynamo and everything else * add test * linter * add test to the script
* Initial commit for debugging tool * minor format tweak * Only master process should print the execution frame info * add execution cause * handle dynamo and everything else * add test * linter * add test to the script
* Initial commit for debugging tool * minor format tweak * Only master process should print the execution frame info * add execution cause * handle dynamo and everything else * add test * linter * add test to the script
* Initial commit for debugging tool * minor format tweak * Only master process should print the execution frame info * add execution cause * handle dynamo and everything else * add test * linter * add test to the script
* Initial commit for debugging tool * minor format tweak * Only master process should print the execution frame info * add execution cause * handle dynamo and everything else * add test * linter * add test to the script
* Initial commit for debugging tool * minor format tweak * Only master process should print the execution frame info * add execution cause * handle dynamo and everything else * add test * linter * add test to the script
FYI @Liyang90 @AlexWertheim
example output