sanitycheck --coverage failed #13729
Assignees
Labels
Milestone
Comments
|
@nashif Any advice please? Many thanks |
nashif
pushed a commit
to wentongwu/zephyr
that referenced
this issue
Mar 3, 2019
This part of tests was forgotten when we move to subsys/ Fixes zephyrproject-rtos#13729 Signed-off-by: Wentong Wu <[email protected]> Signed-off-by: Anas Nashif <[email protected]>
|
this is still broken even after #13982 |
|
at least on ARM |
|
@wentongwu please continue checking about this. |
Hi @nashif : Does mps2_an385 counts as ARM? I do realize at present it is a QEMU emulation but I managed to get a html report using mps2_an385. It also works for me if I substitutes |
the problem is that sanitycheck cannot generate coverage report. From Cinly's console output, all test cases failed because of cmake not finding coverage folder to generate build files. So after the #13982, sanitycheck can work like before. Also before the pull request, I do the test locally and it can fix Cinly's problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
sanitycheck cannot generate coverage report.
To Reproduce
Steps to reproduce the behavior:
scripts/sanitycheck --coverage --coverage-platform mps2_an385 -p mps2_an385 --coverage-platform qemu_x86 -p qemu_x86 --gcov-tool /opt/zephyr-sdk-0.9.5/sysroots/x86_64-pokysdk-linux/usr/bin/i586-zephyr-elf/i586-zephyr-elf-gcov -T tests/kernel/ -T tests/subsys/logging/Expected behavior
A clear and concise description of what you expected to happen.
Impact
Cannot generate coverage report for Triaging.
Screenshots or console output
Environment (please complete the following information):
Additional context
Without coverage options, sanity check runs fine:
scripts/sanitycheck -p mps2_an385 -p qemu_x86 -T tests/kernel/ -T tests/subsys/logging/The text was updated successfully, but these errors were encountered: