-
Notifications
You must be signed in to change notification settings - Fork 132
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
Up2-nocodec: sof-logger / ldc failure in capture/playback test #2361
Comments
Quoting myself from #2357 : We started paying more attention to the sof-logger (and there's more coming, see thesofproject/sof-test#297 and 298) The two failures in https://sof-ci.01.org/linuxpr/PR2357/build4293/devicetest/ look basically the same:
At the bottom of the (long)
|
yeah, doesn't look like an "audio problem" to me either |
ldc failure means that for some reason the active firmware image and ldc file aren't from the same build, or you use an old version of sof-logger that cannot properly decode the ldc file. Sounds like a CI problem. |
it could very well be a CI problem but why would it affect only this platform? |
The test machine maybe has an older version of sof-logger or some misconfiguration. |
Although I think it should have said "ABI mismatch" instead. |
@marc-hb Can you help check this issue? |
@plbossart so what's the issue here? CI provided inaccurate info? |
@Keyon the question is why is the CI machine having incompatible versions of fw and debug file, or is this because of some other reason... |
we have another sof-logger issue #2379 |
@paulstelian97 I think that sof-logger issue is thesofproject/sof#3344, right? |
Took a look and commented on the sof-logger issue. Scratching my head... |
Cannot reproduce in CI recently, so lower the priority. |
The slogger shows it's more likely the *.ldc file has changed during the test. CI hasn't reproduced this issue. So closed it. |
Adding issue to keep track of problem reported here: https://sof-ci.01.org/linuxpr/PR2357/build4293/devicetest/
The text was updated successfully, but these errors were encountered: