[HDDS-8374] Fix Flaky Unit Test for TestContainerStateCounts in Recon

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: Ozone Recon
• Labels: pull-request-available
• Assignee: Arafat Khan
• Reporter: Arafat Khan
• Created: 04/Apr/23 13:49
• Updated: 12/Apr/23 17:49
• Resolved: 12/Apr/23 17:49

Description

The testDeletedContainerCount() method of TestContainerStateCounts is considered flaky due to the processing order of the container report. If the pipeline does not exist, then the container is not added until the next container report is processed.
 

https://github.com/adoroszlai/ozone-build-results/blob/master/2023/04/04/21308/unit/hadoop-ozone/recon/org.apache.hadoop.ozone.recon.api.TestContainerStateCounts.txt

Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.171 s <<< FAILURE! - in org.apache.hadoop.ozone.recon.api.TestContainerStateCounts
org.apache.hadoop.ozone.recon.api.TestContainerStateCounts.testDeletedContainerCount  Time elapsed: 11.103 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <5> but was: <2>
	at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
	at org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)
	at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
	at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
	at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
	at org.apache.hadoop.ozone.recon.api.TestContainerStateCounts.testDeletedContainerCount(TestContainerStateCounts.java:383)

Issue Links

• links to: GitHub Pull Request #4534