-
Notifications
You must be signed in to change notification settings - Fork 29k
print intermediate and raw A/B results when not silent #54676
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
Conversation
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
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.
LGTM. Yes, the test usually takes a very long time for a single run (e.g., 30 seconds) and A/B test is printing very few things regarding that time.
BTW, I just realized that the original PR #54494 doesn't have a unit test. Should this neat A/B test have some unit tests just to make sure that it won't be accidentally broken in the future? |
fae3cf2
to
90e7064
Compare
Done. |
Oops! Hold on! I rebased on top of a wrong branch 🤦 |
90e7064
to
9f897ec
Compare
This is ready for re-review. PTAL. |
e9851a3
to
7e3b116
Compare
Still LGTM! |
Description
Some tests can take a while to run. If
--silent
is not specified, print A/B results for the benchmark iterations that ran so far. It can also be used to set--ab
to something very high, like 100, and then stop the benchmark manually.