Feature/state machine selection #786
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
Trying to make something vaguely matching interface of the linux statemachine to make it easier to pick between them API wise
Decoupling the execution and collecting coverage to make it more suitable for more test launch scenarios
Checksd if ptrace is supported or if llvm coverage is selected and runs the correct state machine. This does add a boxed trait but it's worth it
Next step is converting the profraws and binaries into coverage data
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.
Next step in tarpaulin of llvm cov is to launch tests in different ways and have state machine selection. This PR aims to set up the start of this and is necessary for #549 and #675