-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
subsys: logging: log_core_additional: test_log_domain_id Twister reports fails even the test passed #87625
Comments
that does not make sense. cavs25 does not have ttyACM0 |
sorry, I forgot change this parameter. I changed in description. |
@nashif I appended to the description the logs from up2 and ace15_mtpm |
I think there is at least 2 problems here to investigate and resolve
zephyr/tests/subsys/logging/log_core_additional/src/log_test.c Lines 219 to 222 in ca0f5f6
|
in this case, always are mixed the log message from line 219 and the summary for this test case zephyr/tests/subsys/logging/log_core_additional/src/log_test.c Lines 212 to 226 in ca0f5f6
There is the simple workaround for it:
In the harness Test a status of test case is changed to Failed because regex pattern test_case_end_pattern not match line in a log. zephyr/scripts/pylib/twister/twisterlib/harness.py Lines 909 to 926 in ca0f5f6
|
yeah, (see my comment 2.) and that's exactly why my ask is to reproduce the issue running twister with |
Describe the bug
The fail was observed on platforms:
The twister reporting fail in twister.json file for this test:
but this test passed and the twister.log confirmed it:
In the twister.log we see corrupted line for this test. In the same line we see mixed two lines:
The correct output should seems that:
To Reproduce
have one of above platform connected
go to your zephyr directory and setup env
call ./scripts/twister -T tests/subsys/logging/log_core_additional -p intel_adsp/cavs25 --device-testing --device-serial-pty="$ZEPHYR_BASE/soc/intel/intel_adsp/tools/cavstool_client.py,-s,remotehostname,-l" -v --inline-logs
See console output with test suite passed and all test cases passed but in the twister.json file the test log_domain_id is failed.
Expected behavior
Impact
twister.json file - reporting feature in twister
Environment (please complete the following information):
Additional information
These are logs from up_squared/apollo_lake
and the wrong lines in the twister.log file
The same result as for cavs25 in twister.json file - the test test_log_core_additional.log_domain_id is set as failed
and the same issue on ace15
corrupted lines:
Part of twister.json from this run
The text was updated successfully, but these errors were encountered: