Output log trace of a run to console - #148
Merged
Merged
Conversation
Member
Author
|
Example output |
istathar
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce the technique log subcommand.
This prints a nicely formatted version of the trace of a run. Reading the Procedure interchange Format For Transferring Techniques data from the .pfftt file in the local store corresponding to the given run, render a more human readable version to the console.
In addition to the default
console, there are also--outputoptions forpfftt(as written on disk),json(to output an array of JSON objects), and finally as with other commands anativevariant (for debugging the internal data structures if necessary).The command offers the ability to select the columns being displayed using the
--columnsoption.