-
Notifications
You must be signed in to change notification settings - Fork 273
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
add support for "sai_dbg_generate_dump" API #1423
base: master
Are you sure you want to change the base?
add support for "sai_dbg_generate_dump" API #1423
Conversation
please make build success, after that i will review this |
please rebase to latest master |
Done |
add HLD PR: sonic-net/SONiC#1846 |
@aviramd can you fix whitespaces issue:
|
You will also need to add some unit tests to satisfy code coverage |
0b1dee6
to
c680f50
Compare
i hink you made some mistake, you only touch test file |
Yes you are right , i am working to fix it |
This update introduces support for the sai_dbg_gen_dump API to generate a debug dump file by the SAI The general process is as follows: The filename is written to configDB. This action triggers the dbgGenDumpOrch to write the necessary data to ASIC DB. The syncd process reads from ASIC DB and invokes the SAI. SAI processes the request and returns a response. syncd writes the response back to redis. dbgGenDumpOrch retrieves the response and informs the caller by writing to configDB. The caller then removes the data from configDB.
Signed-off-by: aviramd <[email protected]>
This reverts commit c680f50.
you can try build this on your local machine to check whether it will compile first |
b7bdc69
to
a365865
Compare
I have some git issues on my local machine |
a365865
to
75319be
Compare
Is it possible to execute the sairedis unit test locally? if yes how? |
Yes, type make check in local console |
413ea6b
to
29ea2bb
Compare
6c22b65
to
4295cc6
Compare
08d8937
to
df0f4de
Compare
to avoid so many push commits please test everything locally |
df0f4de
to
e51ff47
Compare
Is this the correct procedure for testing?
Also, after building the target, a cleanup occurs, and the make file (which is auto-generated during the build) gets deleted. How can I prevent this from happening? |
e51ff47
to
747da04
Compare
no, you don't need to build entire docker |
Thank you for your support! I tried running the command locally, but I encountered the following error when execute "make": "libtool: compile: g++ ... -c AttrKeyMap.cpp -fPIC -DPIC -o .libs/libsaimeta_la-AttrKeyMap.o |
Yes you need to install swss-common library also from source |
Thank you very much, I can run the tests now with 'make check'. |
results are done in *gcno *gcna files, but they need to be processed, in azure pipeline gcovr results are colleted and then putt tohether, in pipeline output is done in json, and then module is preenting them in nice form on github, locally you can generate nice html, take a look gcovr help: |
This update adds support for the sai_dbg_gen_dump API, enabling the generation of a debug dump file by the SAI when there is no SAI failure.
add support to the global API
sai_dbg_generate_dump
to theSaiInterface
class.add a new operation to the syncd to support SAI debug generate dump
HLD: sonic-net/SONiC#1846