Enable p4orch unit test for test workflow.#2375
Conversation
mint570
force-pushed
the
p4orch_unit_test
branch
5 times, most recently
from
7722b9d to
d36a171
Compare
mint570
force-pushed
the
p4orch_unit_test
branch
2 times, most recently
from
561edc7 to
18ec850
Compare
mint570
force-pushed
the
p4orch_unit_test
branch
2 times, most recently
from
8164f4e to
39dd2f9
Compare
Change-Id: I43e57820c357507bb29e476ed9c7bf7928aa489a
Change-Id: I2b578e40aaec39eea35afafd47bbfb7930efec37
Change-Id: Iad9510e2f1408c0de2ef5f952d1139c0bf1e050b
mint570
force-pushed
the
p4orch_unit_test
branch
4 times, most recently
from
fee8813 to
f4ea92a
Compare
mint570
force-pushed
the
p4orch_unit_test
branch
from
f4ea92a to
47be3d7
Compare
|
@prsunny @theasianpianist |
|
Thanks @mint570 for this PR. Can you please provide a generic PR that can enable code coverage for the unit-tests? Currently that is missing. |
If the unit test is run in debian build, the code coverage will be included after this PR. We explicitly exclude certain test files in the final report. (They are just unit test codes. This is to stop the coverage complain on unit test codes and fake codes.): |
* Enable p4orch unit test for test workflow. * Add unit test coverage into coverage report. * Remove unit test files from coverage report.
* Enable p4orch unit test for test workflow. * Add unit test coverage into coverage report. * Remove unit test files from coverage report.
3 participants
What I did
Enable p4orch unit test for test workflow. This will run the p4orch unit test and sanitizer test. It will also include the p4orch unit test coverage into the swss code coverage.
Why I did it
Today the p4orch unit test does not run. And the coverage data is not included.
How I verified it
Presubmit run.
Details if related