-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Update swss and sairedis modules together to break dependency on each other #22019
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update swss and sairedis modules together to break dependency on each other #22019
Conversation
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
* Due to dependencies, both need to be updated together Signed-off-by: Prabhat Aravind <[email protected]>
bbee85f
to
7cec28f
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
@prabhataravind @prsunny @kcudnik
other issues do not seem like relevant to swss/sairedis change
|
Thanks @stephenxs for the input. @prabhataravind , can we rebase to latest sairedis commit? |
@prsunny @stephenxs, PRs sonic-net/sonic-sairedis#1548 and sonic-net/sonic-sairedis#1549 are not yet merged. Once merged, I can try rebasing to the latest sairedis master. |
Signed-off-by: Prabhat Aravind <[email protected]>
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Prabhat Aravind <[email protected]>
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yxieca , please merge
@prabhataravind , please update commit messages in description. Reference - #22340 |
… other (sonic-net#22019) Update swss submodule to a07838d : [[orchagent] Do not restore port admin if port admin is configured Update sairedis submodule to 7a7320a : [[syncd] Move log set function after api initialize Why I did it PR sonic-net/sonic-swss#3391 has a dependency on sonic-net/sonic-sairedis#1519 and therefore the two submodules need to be updated together. How I did it By updating both swss and sairedis submodules together. How to verify it Ran sanity checks on kvm testbeds
… other (sonic-net#22019) Update swss submodule to a07838d : [[orchagent] Do not restore port admin if port admin is configured Update sairedis submodule to 7a7320a : [[syncd] Move log set function after api initialize Why I did it PR sonic-net/sonic-swss#3391 has a dependency on sonic-net/sonic-sairedis#1519 and therefore the two submodules need to be updated together. How I did it By updating both swss and sairedis submodules together. How to verify it Ran sanity checks on kvm testbeds
src/sonic-swss
src/sonic-sairedis
Why I did it
PR sonic-net/sonic-swss#3391 has a dependency on sonic-net/sonic-sairedis#1519 and therefore the two submodules need to be updated together.
Work item tracking
How I did it
By updating both swss and sairedis submodules together.
How to verify it
Ran sanity checks on kvm testbeds
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Update swss and sairedis modules together to break dependency on each other.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)