Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
Patch Available
-
Unit Test Broken
Description
This test fails intermittently at a point where it expects BrokerView.getMemoryPercentUsage() to return 0, but it returns 1. The problem here is that getMemoryPercentageUsage returns an int, and that number is truncated when calculated.
I did some debugging and found when the test fails the actual usage is about 0.85%, and when it fails it's only 1.02%. I'll attach a patch that makes the assertion here slightly more lenient to accommodate for this.