Add ordering after data normalization. #112
Merged
Conversation
This file contains 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
pszulczewski
requested review from
chadell,
lvrfrc87,
scetron and
jeffkala
as code owners
lvrfrc87
previously approved these changes
Jan 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some device commands elements may come in different order between pre and post check, especially when a device is rebooted after SW upgrade. This behavior was observed for
show lldp neighborswhen the order is different after reload what leads to failed post-check.This PR adds key sorting when data normalization is used with key anchoring.
Tests have been extended to cover that LLDP case with different order of neighbors between pre and post checks.
Updates in
test_operators.pyjust change the order of elements in expected results.