-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
samples/subsys/logging/logger timeout when sanitycheck enable coverage, it needs a filter #27396
Comments
As a remark, I have no experience with the coverage usage, so what I am writing might have not much sense. |
@PerMac For the other testcases, the program will dump coverage data by calling It will take a long time to output all the coverage information, so the sanitycheck can't get the testcase state when timeout.
|
@PerMac Is this a mistake? Here should be zephyr/scripts/sanity_chk/sanitylib.py Line 3268 in 9df168b
|
@wangnuannuan Yes: #27474 |
@wangnuannuan I cannot reproduce the issue with the timeout on my PC. the code executes in time.
Then you can compare run times with and without |
@PerMac I test it with
The log information indicates that And following is the log of
|
Do I need something extra installed to use |
I think maybe the first thing to do is to make sure that only zephyr logger can call
|
This can be folded in #27573 |
Describe the bug
When enable coverage, sanitycheck fails to get coverage data from
samples/subsys/logging/logger
.The coverage data will be output by
log_printk
, because theCONFIG_LOG_PRINTK
is enable, so the coverage data is treated as a log data.zephyr/subsys/testsuite/coverage/coverage.c
Line 211 in ee525c2
zephyr/lib/os/printk.c
Line 453 in 83b9f69
The text was updated successfully, but these errors were encountered: