Add serial console stress test #21587
Open
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:
Fixes #21134
This test exercises the console of a SONiC Device by pushing a large block of data into the console as well as generate a large block of of output out of the console to ensure that console remains stable.
This test supports all form factors including fixed and modular. On a modular system (Currently only supports Arista, but can easily be extend to to other systems), it exercises both the supervisor and the linecard console.
This requires extending the related fixtures to create a LinecardConsoleConn helper that can encapsulate the console interaction on a linecard, which requires architecture specific adaptation.
Type of change
Back port request
Approach
What is the motivation for this PR?
This test verifies the stability of the serial console under load.
How did you do it?
This pushes a large block of data into the console as well as generate a large block of of output out of the console to ensure that console remains stable.
This requires extending the related fixtures to create a LinecardConsoleConn helper that can encapsulate the console interaction on a linecard, which requires architecture specific adaptation.
How did you verify/test it?
This test has been verified on Arista platform.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation