-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Cannot generate code coverage report for unit tests using sanitycheck #24674
Labels
area: Sanitycheck
Sanitycheck has been renamed to Twister
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Comments
thoh-ot
added
bug
The issue is a bug, or the PR is fixing a bug
area: Sanitycheck
Sanitycheck has been renamed to Twister
area: Testing
labels
Apr 24, 2020
AFAIK coverage is only supported when you use |
This is the error I get; not sure if it's what was observed.
|
nashif
added a commit
to nashif/zephyr
that referenced
this issue
Apr 28, 2020
Fix setting coverage for unit tests and link against gcov when coverage is enabled. Fixes zephyrproject-rtos#24674 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
nashif
added a commit
that referenced
this issue
Apr 29, 2020
Fix setting coverage for unit tests and link against gcov when coverage is enabled. Fixes #24674 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
sandeepbrcm
pushed a commit
to Broadcom/zephyr
that referenced
this issue
Apr 30, 2020
Fix setting coverage for unit tests and link against gcov when coverage is enabled. Fixes zephyrproject-rtos#24674 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
hakehuang
pushed a commit
to hakehuang/zephyr
that referenced
this issue
Jun 20, 2020
Fix setting coverage for unit tests and link against gcov when coverage is enabled. Fixes zephyrproject-rtos#24674 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: Sanitycheck
Sanitycheck has been renamed to Twister
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Code coverage rapport for the unit tests in Zephyr.
Impact
Annoyance; we wan't to introduce new unit tests of the Zephyr Bluetooth controller code and the coverage rapport is a very valuable tool in that matter.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: