[action] [PR:14788] Retry test_psu.py::TestPsuApi::test_power if power not within tolerance #15587
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
If
test_psu.py::TestPsuApi::test_power
fails onabs(power - (voltage*current)) < power*0.1
then retry the test. The test is repeated for a maximum of three times until it passes, else it is failed. This change is introduced to account for the stringent tolerance level of 10% and the errors that might be caused due to time differences in reading each of the parameters (current, voltage and power).Fixes # (issue)
Addresses issue: https://github.com/aristanetworks/sonic-qual.msft/issues/209
Type of change
Back port request
Approach
What is the motivation for this PR?
Improve the test to account for stringent tolerance level and asymmetric reading of parameters for power calculation.
How did you do it?
If the test fails for the condition
abs(power - (voltage*current)) < power*0.1
, the test will collect fresh parameters (voltage, current and power) from the PSU telemetry and recheck the condition. It is limited to a maximum of 3 attempts.How did you verify/test it?
Tested internally by varying the tolerance level and verifying the number of api calls.
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
N/A
Documentation
N/A