-
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
Flaky-test: PerformanceTransactionTest.testConsumeTxnMessage #14109
Comments
The test is flaky that was introduced by the changes in #11933. @liangyepianzhou would you mind taking a look at #14109 ? Thank you |
This is an unstable test caused by message retransmissions. I think it should be possible to fix this test by reducing the accuracy. I'll give a PR with the fix later. |
Thanks @liangyepianzhou , that would be great. |
The issue had no activity for 30 days, mark with Stale label. |
The issue had no activity for 30 days, mark with Stale label. |
@liangyepianzhou Do you want to push a PR to fix the issue? |
* [Fix][Flaky-test] Fix testConsumeTxnMessage Master #14109 ## Motivation The transaction commit is async, so the consumer can still receive message when the consumer rebuilds. ## Modification Add Awaitility.await() for check-ing whether the ongoingTxns = 0.
* [Fix][Flaky-test] Fix testConsumeTxnMessage Master #14109 ## Motivation The transaction commit is async, so the consumer can still receive message when the consumer rebuilds. ## Modification Add Awaitility.await() for check-ing whether the ongoingTxns = 0.
* [Fix][Flaky-test] Fix testConsumeTxnMessage Master apache#14109 ## Motivation The transaction commit is async, so the consumer can still receive message when the consumer rebuilds. ## Modification Add Awaitility.await() for check-ing whether the ongoingTxns = 0.
The flaky test still happens on the master branch https://github.com/apache/pulsar/runs/7899134537?check_suite_focus=true, reopen the ticket. @liangyepianzhou Could you please help check again? |
* [Fix][Flaky-test] Fix testConsumeTxnMessage Master apache#14109 ## Motivation The transaction commit is async, so the consumer can still receive message when the consumer rebuilds. ## Modification Add Awaitility.await() for check-ing whether the ongoingTxns = 0. (cherry picked from commit c29503e) (cherry picked from commit 6db6679)
…7837) Fixes: #14109 ### Motivation The expected execution flow for this test is: 1. send 505 messages 2. commit 10 transactions, every transaction ack 50 messages 3. receive the last 5 messages in the last transaction, wait for transaction timeout 4. confirm that the last 5 messages can be consumed by new consumer <strong>(High light)</strong> The default value for transaction TTL is 10 seconds, and the default value for `Awaitility.await` is also 10 seconds, so this test is not stable. Note: This is a guess cause, the problem is not reproduced locally. But after transaction TTL is set to 11s, the probability of the problem occurring is 100%. ### Modifications Fix flaky test - set transaction TTL to 5s Other changes - define a name for the task thread - acknowledge the last 5 messages ### Matching PR in forked repository PR in forked repository: - poorbarcode#13
Flaky-test: org.apache.pulsar.testclient.PerformanceTransactionTest.testConsumeTxnMessage
Number of failures: 5
org.apache.pulsar.testclient.PerformanceTransactionTest is flaky. The testConsumeTxnMessage test method fails sporadically.
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click.
example failure 2022-02-02T16:48:35.3692126Z
Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click.
example failure 2022-01-29T05:03:33.6909916Z
Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click.
example failure 2022-01-28T12:46:12.5203828Z
Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click.
example failure 2022-02-02T13:38:31.6649715Z
Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click.
example failure 2022-01-29T05:24:40.1685311Z
Full exception stacktrace
The text was updated successfully, but these errors were encountered: