-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Change pycommon to use swsscommon #10099
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
Change pycommon to use swsscommon #10099
Conversation
py_common change will break UT in sonic-platform-daemons, the issue will be fix in this PR: sonic-net/sonic-platform-daemons#246 |
This pull request introduces 1 alert when merging f21d1c8 into c40f04f - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 45d60b1 into 2ef9d65 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 5a5f592 into 78e867a - view on LGTM.com new alerts:
|
/azp run Azure.sonic-buildimage |
Pull request contains merge conflicts. |
This PR is continue of original PR: #7655 |
This pull request introduces 1 alert when merging 1a3a020 into 8601709 - view on LGTM.com new alerts:
|
I notice the filename not proper https://github.com/Azure/sonic-buildimage/blob/8d419ca2c59b0f75c24ba4ed73fbdc7df7812260/src/sonic-py-common/tests/device_info_test.py#L16. Change mock_swsssdk to mock_swsscommon In reply to: 1065633693 Refers to: src/sonic-py-common/sonic_py_common/device_info.py:1 in 1a3a020. [](commit_id = 1a3a020, deletion_comment = False) |
Azure Pipelines successfully started running 1 pipeline(s). |
…stcfgd_to_swsscommon
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
…stcfgd_to_swsscommon
After merge with latest master branch code, only 1 UT failed and seems not related with code change in this PR: bgp/test_bgp_update_timer.py |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
After re-run, still following UT failed: And same UT failed happened on many other PRs, seems a common issue, will re-run later. |
/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). |
@@ -4,6 +4,8 @@ ifeq ($(ENABLE_PY2_MODULES), y) | |||
SONIC_PY_COMMON_PY2 = sonic_py_common-1.0-py2-none-any.whl | |||
$(SONIC_PY_COMMON_PY2)_SRC_PATH = $(SRC_PATH)/sonic-py-common | |||
$(SONIC_PY_COMMON_PY2)_DEPENDS += $(SWSSSDK_PY2) | |||
$(SONIC_PY_COMMON_PY2)_DEBS_DEPENDS = $(LIBSWSSCOMMON) \ |
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.
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.
Fixed, remove indirect dependency to LIBSWSSCOMMON.
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.
you fixed py3, but py2 still has the same issue.
@liuh-80, @qiluo-msft Can this be backported to 202205? 202205 is still using swsssdk I've observed some perf difference when running "intfutil -c status".
|
Request for 202205 |
@vivekrnv @dgsudharsan Backport of this feature include many PRs in multiple repos, and with dependencies between them. If there is no strong motivation, we will not backport to 202205 and earlier branches. |
Thought so looking at the other comments, the only motivation is perf diff, nothing else |
Why I did it
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)