Clean up the benchmark suite #668
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
aaronayres35
approved these changes
Mar 3, 2021
|
Thanks for the review |
rahulporuri
moved this from Done
to Sprint 4 : March 1 - March 12 2021
in Enthought OSS Q1 2021
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.
#666 was pretty exhausting to implement because of all the output differences introduced by non-GUI backends.
This is a general cleanup of the benchmark code, with emphasis on the
publishfunction and introducing some real objects for the result data to hopefully make things a little more readable.After this, I think the only thing left is to increase the size of the suite (ala #667) and more importantly, use the results as guidance for fixing problems and harmonizing backend outputs.