-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[fix][flaky-test] fix flaky test PerformanceTransactionTest
#18296
Conversation
@poorbarcode Please also help review this PR. |
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.
But notice -r 10 set the consumption rate limit to be 10 msg per second, so every transaction is about 5 seconds. In #17837 we set the transaction TTL to be 5 seconds
Yes, that is the root cause. Each transaction cost 5s and the timeout is 5s.
@liangyepianzhou Do we need the slow commit here?
If need that,. we can set -r 50
to resolve this problem.
@poorbarcode Good idea, I also prefer to modify it to -r 50 which can make the test more comprehensive. |
OK, I'll do this @liangyepianzhou |
Codecov Report
@@ Coverage Diff @@
## master #18296 +/- ##
=============================================
+ Coverage 38.97% 52.03% +13.06%
+ Complexity 8311 7419 -892
=============================================
Files 683 400 -283
Lines 67325 43682 -23643
Branches 7217 4479 -2738
=============================================
- Hits 26239 22730 -3509
+ Misses 38079 18512 -19567
+ Partials 3007 2440 -567
Flags with carried forward coverage won't be shown. Click here to find out more.
|
PTAL @liangyepianzhou |
PerformanceTransactionTest
Fixes #18282
Modifications
We start 10 transactions and consume 50 messages in every transaction by default.
But notice
-r 10
set the consumption rate limit to be 10 msg per second, so every transaction is about 5 seconds.In #17837 we set the transaction TTL to be 5 seconds, so transactions may be timeout randomly, which causes the test to fail.
To prove this, you can try to set
-r 9
or-tto 4
, which will cause failure 100%.So remove the
-r
option can fix this issue.Verifying this change
Documentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: labuladong#6