Repository navigation
mux: remove the wrong error message - #4174
Conversation
|
@lgirdwood @keqiaozhang @XiaoyunWu6666 this is a quick fix to issues like below happens in daily report: |
There was a problem hiding this comment.
@keyonjie the change looks good. But I wonder if the return 0 at the of the function is correct? If a match is not found, we should return a negative value isn't it?
There was a problem hiding this comment.
@keyonjie the change looks good. But I wonder if the return 0 at the of the function is correct? If a match is not found, we should return a negative value isn't it?
That's a good point. I think the intention of the original author just wanted to return and use the first index (0) if the matched one not found, please check in the caller side, they don't check the return value and just use it as index blindly.
There was a problem hiding this comment.
Actually this is unsafe as it's used for an array lookup and may assign a source/sink for usage that is not in the correct state (and may crash etc). Can we check the result and return an error here (and handle it in the caller.)
There was a problem hiding this comment.
Actually this is unsafe as it's used for an array lookup and may assign a source/sink for usage that is not in the correct state (and may crash etc). Can we check the result and return an error here (and handle it in the caller.)
Sure, let me add a commit to address this.
lgirdwood
left a comment
There was a problem hiding this comment.
Good find and review comments, but we need to treat and handle the error.
|
updated. Hi @marc-hb looks the imx qemu-boot-test fail, how can I get more info about that? |
|
SOFCI TEST |
There was a problem hiding this comment.
Please use idx instead of i.
|
SOFCI TEST |
|
qemu boot test failure for imx doesn't make much sense. Because this patch doesn't touch anything sensible to boot. Did something change with docker? |
|
please test this |
|
@lgirdwood what's the magic incantation to retrigger CI? |
Yes there's been an Ubuntu upgrade very recently https://github.com/thesofproject/sof/commits/main/scripts/docker_build https://hub.docker.com/r/thesofproject/sof/tags
It depends which CI. The only way to retrigger all of them is to Github Actions can be re-run from the "checks" tab. |
The QEMU test waits for some time, then it checks whether some expected output got printed. That expected output never came so the test failed for IMX. It should be easy to reproduce locally by running the commands at: If using the previous docker image tag gets this test passing again then we can just revert CI to that previous tag until the problem is fixed. cc: @fredoh9 |
Thanks, but seems it re-run the "On-device Testing" for me also... |
A wrong error message was added in helper get_stream_index(), remove to fix it. Fixes: 80666b7 ("ipc: component: abstract the component creation API") Signed-off-by: Keyon Jie <yang.jie@linux.intel.com>
We should return error if the matching in get_stream_index() fail, add check in the callers, stop using it and return failure when needed. Signed-off-by: Keyon Jie <yang.jie@linux.intel.com>
Oh, I just realized that 'SOFCI TEST' doesn't work for me anymore while it worked previously, this is not a user friendly change IMHO. |
|
I did not realize that SOFCI TEST was going away, but I can now see the check tab and I've clicked rerun tests (which I assume everyone can see ?) Please shout if you cant see this button in the check tab. |
|
@fredoh9 @marc-hb ok - I see 2 CI problems.
|
lgirdwood
left a comment
There was a problem hiding this comment.
There is nothing here that should break IMX or Zephyr build. Safe to merge until we figure out whats breaking CI infrastructure here.
I can see it but looks what I can choose is only "Re-run all jobs", is that same at your end? |
Yep - I can see the same. |
|
Ok, Zephyr CI fix is now merged. |
|
@lgirdwood will try to increase the timeout. but i'm quite busy this days. @paulstelian97 if you have some spare cycles maybe you can investigate. I think you can run the entire usecase as CI does: Just try to see if increasing the timeout fixes the problem. |
What makes you think it does not work? |
|
@marc-hb i tried it several times and none of the CI tasks started. |
|
These keywords have only ever been scanned by Jenkins and there are many Jenkins run in https://sof-ci.01.org/sofpr/PR4174/ |
@fredoh9 reproduced the issue, reverted the docker image and file new QEMU IMX issue #4186. See you there! |
|
For the keyword, we never disable or change it. But SOF Jenkins server have been throttled, so response may be slow sometimes. |
I just tried it here again and it worked: https://sof-ci.01.org/softestpr/PR544/ , thesofproject/sof-test#544 If you have examples with specific URLs and exact timings then please share. |
A wrong error message was added in helper get_stream_index(), remove to
fix it.
Fixes: 80666b7 ("ipc: component: abstract the component creation API")
Signed-off-by: Keyon Jie yang.jie@linux.intel.com