Fixed issues with GNOI System Reboot Tests #16730
Closed
Conversation
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
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
e1f2191 to
eb470f0
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
eb470f0 to
2595d6a
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
2595d6a to
a0cf1b6
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
a0cf1b6 to
6c553c3
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
24ed065 to
c13c505
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
c13c505 to
c6c6ad6
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
c6c6ad6 to
35b3591
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
No need to change the test infrastructure, you can disable log analyzer here like this: |
Contributor
|
Also can you merge the PR into this branch rather than the upstream master? https://github.com/hdwhdw/sonic-mgmt/tree/reboot This is the branch behind the PR #16576 |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
35b3591 to
ba4c6b7
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
ba4c6b7 to
d23d9ae
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kanchanavelusamy
force-pushed
the
gnoi_reboot_tests
branch
from
d23d9ae to
f0063b8
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
@hdwhdw I’ve created a new PR targeting hdwhdw:reboot as requested: [New PR Link]. Let me know if you need any modifications. |
Author
|
PR rebased to https://github.com/hdwhdw/sonic-mgmt/tree/reboot and merged into #16576. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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
Summary: Skip GNMI recovery during teardown if reboot was triggered"
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation