Skip to content

Try to fix flaky test in the InactiveTopicDeleteTest.java#8392

Merged
codelipenghui merged 10 commits intoapache:masterfrom
315157973:test
Oct 28, 2020
Merged

Try to fix flaky test in the InactiveTopicDeleteTest.java#8392
codelipenghui merged 10 commits intoapache:masterfrom
315157973:test

Conversation

@315157973
Copy link
Contributor

1)testTopicLevelInActiveTopicApi:The error is caused by getInactiveTopicPolicies(), due to the slow startup of the broker, the cache has not been initialized yet.

2)testTopicLevelInactivePolicyUpdateAndClean:We previously updated the event trigger timing of topic-policies. The update is triggered after the event is consumed. Therefore, it is not enough to judge that the policy in the cache is null. We need to sleep and wait for the event to be consumed.

@315157973
Copy link
Contributor Author

The second problem has been fixed, the first one I will comment out some code to see what the real error is

@codelipenghui
Copy link
Contributor

/pulsarbot run-failure-checks

@codelipenghui codelipenghui merged commit 98bd0c2 into apache:master Oct 28, 2020
huangdx0726 pushed a commit to huangdx0726/pulsar that referenced this pull request Nov 13, 2020
1)testTopicLevelInActiveTopicApi:The error is caused by `getInactiveTopicPolicies()`, due to the slow startup of the broker, the cache has not been initialized yet.

2)testTopicLevelInactivePolicyUpdateAndClean:We previously updated the event trigger timing of topic-policies. The update is triggered after the event is consumed. Therefore, it is not enough to judge that the policy in the cache is null. We need to sleep and wait for the event to be consumed.
flowchartsman pushed a commit to flowchartsman/pulsar that referenced this pull request Nov 17, 2020
1)testTopicLevelInActiveTopicApi:The error is caused by `getInactiveTopicPolicies()`, due to the slow startup of the broker, the cache has not been initialized yet.

2)testTopicLevelInactivePolicyUpdateAndClean:We previously updated the event trigger timing of topic-policies. The update is triggered after the event is consumed. Therefore, it is not enough to judge that the policy in the cache is null. We need to sleep and wait for the event to be consumed.
@315157973 315157973 deleted the test branch November 28, 2020 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments