Feature deterministic results parser #12
Open
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
gruberma
force-pushed
the
master
branch
6 times, most recently
from
9f74641
to
6344fda
Compare
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.
Adresses issue #9
The results_parser should now sort the data frames according to certain keys:
-test_overview changes the data type of verdicts to tuple in order to enable sorting, because the values must be hashable. Using lists or sets caused an error: TypeError: unhashable type: 'set / list'
-classification_template sorts by Project_Name, Project_URL, Project_Hash and Test_name in ascending order
-passed_failed sorts by Passed_sameOrder and Passed_randomOrder
If there is no necessity for passed_failed (L. 979) to be sorted, you can probably delete this line.