Feature/376 compact tracing #418
Merged
Conversation
This file contains 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
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.
This PR changes the internal data structure to represent an execution trace from a tree to a DAG. This allows for the possibility to perform multiple traces at the same time while reusing subtraces. One can access that feature from the CLI by providing a semicolon separated list to the
tracecommand. Furthermore, this implements the json output format described in #403. This is accessible via a new commandtrace-output [filename].I have also allowed a method to transform the new representation into the old tree-like structure to not break the python api. But maybe this should change now as well.
Fixes #376.
Fixes #403.