-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.13.z, 4.12.z, 4.11.z, 4.10.z, 4.14
-
No
-
False
-
This is a clone of issue OCPBUGS-15800. The following is the description of the original issue:
—
Description of problem:
lately some of the latency tests were failing and it turned out that the failure is due to that the maximum latency found was greater than anticipated. The tests in this suite do not care about the measured latency because we do not care to tune the systems in the first place. Its only goal is to run the tests of the latency tools with different values of environment variables and validate that the tool actually runs with these parameters. Increase the maximum latency threshold so that the test doesn't fail in case of a high latency result. gomega truncating: When the tests fail, we want to have a clear full log of the output of the executed latency tool. The default format.MaxLength is 4000 but it isn't always sufficient to display the full string presentation especially when there is a failure. Disable this limitation by setting the format.MaxLength to 0, to help with better troubleshooting of the failure. For more info: https://onsi.github.io/gomega/#adjusting-output
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-15800 4.12 Latency testing: increase latency threshold and disable gomega truncating
- Closed
- is blocked by
-
OCPBUGS-15800 4.12 Latency testing: increase latency threshold and disable gomega truncating
- Closed
- links to