-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[sonic-slave]: Add gmock for sonic-swss-common tests #8950
Conversation
@lguohan the 2 tests that are failing are unlikely caused by this change. Is there anyway to push this forward? It will ultimately block a PR that will go into sonic-swss-common for the PINs integration. |
/azp run |
Commenter does not have sufficient privileges for PR 8950 in repo Azure/sonic-buildimage |
7dbf672
to
895a55e
Compare
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
Signed-off-by: Don Newton <don@opennetworking.org>
895a55e
to
a4fb693
Compare
Rebased to latest master to retrigger test run |
@lguohan @yxieca Please help us backport this to 202106 and 202012. Currently all active branches share the same Docker tag: Longer term, we should fix this, but for now, this is causing trouble for PINS. Specifically, if the 202012 container is the most recently pushed, we are missing gmock. There should be no harm/risk associated with backporting this change. Thanks! |
Sonic-swss-common requires gmock for staged unit tests Signed-off-by: Don Newton <don@opennetworking.org>
Signed-off-by: Don Newton don@opennetworking.org
Why I did it
Sonic-swss-common requires gmock for staged unit tests
How I did it
Installed dependency in sonic-buster-build docker file
How to verify it
rebuild the build container