-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeQueue: automated test coverage #388
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks great! Mostly nits.
Let's merge #374 first, then make sure this class has the same amount of coverage. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that #374 is landed, let's take the best aspects of both PRs and apply them to both test suites.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Let's follow-up with another PR later to make both test suites more similar.
When I ran this., FreeQueue was significantly faster than FreeQueueSAB (about 2x). Is that what you were seeing too? We have to be a bit careful about reading too much into the results because this isn't a very accurate timing method though.
Please merge when you are ready.
Yeah Sure! Hmm, I am not sure but yes there was some difference. I'll look into that. Sure, we can merge this PR and I'll raise a new PR for extending the SAB TestCases and resolve some nits. |
Sorry, didn't realize you weren't authorized! |
Fixes #347