-
Notifications
You must be signed in to change notification settings - Fork 45
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
[FEATURE] support dictionary formats with "mtrace" #1046
Labels
area:logs
Log and results collection, storage, etc.
P1
Blocker bugs or important features
type:enhancement
New framework feature or request
Comments
kv2019i
added
type:enhancement
New framework feature or request
area:logs
Log and results collection, storage, etc.
labels
May 29, 2023
marc-hb
added
P2
Critical bugs or normal features
P1
Blocker bugs or important features
and removed
P2
Critical bugs or normal features
labels
May 29, 2023
This will require an overdue and significant cleanup of the log collection in sof-test, which may depend on: |
Merged
marc-hb
changed the title
[FEATURE] support dictionary formats with "mtrace" in check-sof-logger.sh
[FEATURE] support dictionary formats with "mtrace"
Jul 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:logs
Log and results collection, storage, etc.
P1
Blocker bugs or important features
type:enhancement
New framework feature or request
Is your feature request related to a problem? Please describe.
Related to thesofproject/sof#7703
When SOF is built is one of the Zephyr dictionary logging formats enabled for mtrace backend, the data seen my mtrace-reader.py will be binary and current check-sof-logger.sh test will fail to detect the Zephyr banner and test case will fail.
sof-test cases need to be extended to handle SOF FW builds where logging output is binary, use appropriate postprocessing tools to decode the binary stream and correctly detect working/non-working FW logging.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: