Skip to content
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

Closed
plbossart opened this issue Aug 13, 2020 · 15 comments
Closed

Up2-nocodec: sof-logger / ldc failure in capture/playback test #2361

plbossart opened this issue Aug 13, 2020 · 15 comments
Assignees
Labels
APL Applies to ApolloLake platform bug Something isn't working P3 Low-impact bugs or features

Comments

@plbossart
Copy link
Member

Adding issue to keep track of problem reported here: https://sof-ci.01.org/linuxpr/PR2357/build4293/devicetest/

@plbossart
Copy link
Member Author

@marc-hb @lyakh FYI.

@plbossart plbossart added the APL Applies to ApolloLake platform label Aug 13, 2020
@marc-hb
Copy link
Collaborator

marc-hb commented Aug 13, 2020

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:

2020-08-13 01:58:18 UTC [REMOTE_ERROR] sof-logger was already dead  # (new test)

At the bottom of the (long) slogger tab:

error: Invalid filename length or ldc file does not match firmware

@marc-hb marc-hb changed the title Up2-nocodec: CI reported capture/playback failures Up2-nocodec: sof-logger / ldc failure in capture/playback test Aug 13, 2020
@marc-hb marc-hb added the bug Something isn't working label Aug 13, 2020
@lyakh
Copy link
Collaborator

lyakh commented Aug 14, 2020

2020-08-13 01:58:18 UTC [REMOTE_ERROR] sof-logger was already dead  # (new test)
error: Invalid filename length or ldc file does not match firmware

yeah, doesn't look like an "audio problem" to me either

@paulstelian97
Copy link

paulstelian97 commented Aug 14, 2020

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.

@plbossart
Copy link
Member Author

it could very well be a CI problem but why would it affect only this platform?

@paulstelian97
Copy link

The test machine maybe has an older version of sof-logger or some misconfiguration.

@paulstelian97
Copy link

Although I think it should have said "ABI mismatch" instead.

@mengdonglin mengdonglin added the P2 Critical bugs or normal features label Aug 17, 2020
@mengdonglin
Copy link
Collaborator

@marc-hb Can you help check this issue?

@keyonjie
Copy link

@plbossart so what's the issue here? CI provided inaccurate info?

@juimonen
Copy link

@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...

@plbossart
Copy link
Member Author

we have another sof-logger issue #2379
This really pollutes our CI results, needs to be fixed.

@mengdonglin
Copy link
Collaborator

we have another sof-logger issue #2379
This really pollutes our CI results, needs to be fixed.

@paulstelian97 I think that sof-logger issue is thesofproject/sof#3344, right?

@paulstelian97
Copy link

Took a look and commented on the sof-logger issue. Scratching my head...

@mengdonglin mengdonglin added P3 Low-impact bugs or features and removed P2 Critical bugs or normal features labels Nov 23, 2020
@mengdonglin
Copy link
Collaborator

Cannot reproduce in CI recently, so lower the priority.

@mengdonglin
Copy link
Collaborator

The slogger shows it's more likely the *.ldc file has changed during the test. CI hasn't reproduced this issue. So closed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APL Applies to ApolloLake platform bug Something isn't working P3 Low-impact bugs or features
Projects
None yet
Development

No branches or pull requests

7 participants