[action] [PR:12941] Include advanced-reboot ptf exception in pytest assertion#12972
Merged
mssonicbld merged 1 commit intosonic-net:202311from May 24, 2024
Merged
Conversation
…12941) What is the motivation for this PR? Surface more information in our test reporting infrastructure to aid in debugging How did you do it? Added more information to a pytest assertion. How did you verify/test it? Artificially added an exception to the try-except block and saw that it was printed out in the pytest assertions.
8 tasks
Collaborator
Author
|
Original PR: #12941 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
This allows the ptf exception to be reported in the Summary field of the V2TestCases table in Kusto.
ADO: 28078972
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Surface more information in our test reporting infrastructure to aid in debugging
How did you do it?
Added more information to a pytest assertion.
How did you verify/test it?
Artificially added an exception to the try-except block and saw that it was printed out in the pytest assertions.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation