Fix smart interval 8-16-stable failure
What does this MR do?
It seems this build is flakey because of its use of long timers.
This needs to be refactored to make sure we're using short-as-possible timers, to avoid unexpected behaviour like this.
This current change is not the best, it would be ideal to test that it reaches the maxInterval and then doesn't go over that. But this is better than completely removing the test as if the timeout finishes early, it still passes, but if the timeout reaches max duration and is higher than the maxInterval, that is a valid failure and this will still fail
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together