Skip to content
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 testEnableAndDisableTopicDelayedDelivery #11009

Merged
merged 2 commits into from
Jun 22, 2021

Conversation

315157973
Copy link
Contributor

Motivation

When admin.topics().getDelayedDeliveryPolicy(topicName) is executed, topicPolicies may not be initialized yet

This problem occurs when only a single unit test is executed.
When the entire unit test is executed, it rarely appears, because other unit tests initialize the TopicPolicies under this Namespace

@codelipenghui codelipenghui added this to the 2.9.0 milestone Jun 22, 2021
@315157973 315157973 merged commit 96b293a into apache:master Jun 22, 2021
eolivelli pushed a commit that referenced this pull request Jun 22, 2021
When admin.topics().getDelayedDeliveryPolicy(topicName) is executed, topicPolicies may not be initialized yet

This problem occurs when only a single unit test is executed.
When the entire unit test is executed, it rarely appears, because other unit tests initialize the TopicPolicies under this Namespace

(cherry picked from commit 96b293a)
@eolivelli eolivelli added the cherry-picked/branch-2.8 Archived: 2.8 is end of life label Jun 22, 2021
yangl pushed a commit to yangl/pulsar that referenced this pull request Jun 23, 2021
When admin.topics().getDelayedDeliveryPolicy(topicName) is executed, topicPolicies may not be initialized yet

This problem occurs when only a single unit test is executed.
When the entire unit test is executed, it rarely appears, because other unit tests initialize the TopicPolicies under this Namespace
codelipenghui pushed a commit that referenced this pull request Jun 27, 2021
When admin.topics().getDelayedDeliveryPolicy(topicName) is executed, topicPolicies may not be initialized yet

This problem occurs when only a single unit test is executed.
When the entire unit test is executed, it rarely appears, because other unit tests initialize the TopicPolicies under this Namespace

(cherry picked from commit 96b293a)
@codelipenghui codelipenghui added the cherry-picked/branch-2.7 Archived: 2.7 is end of life label Jun 27, 2021
@315157973 315157973 deleted the flaky-delivery branch July 19, 2021 11:10
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
When admin.topics().getDelayedDeliveryPolicy(topicName) is executed, topicPolicies may not be initialized yet

This problem occurs when only a single unit test is executed.
When the entire unit test is executed, it rarely appears, because other unit tests initialize the TopicPolicies under this Namespace
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-picked/branch-2.7 Archived: 2.7 is end of life cherry-picked/branch-2.8 Archived: 2.8 is end of life release/2.7.3 release/2.8.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants