-
Notifications
You must be signed in to change notification settings - Fork 48
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] testbench support for IPC4 #1177
Comments
I searched email and found this: |
Just like any other Kconfig? Or am I missing something? To build different Kconfigs then just build twice as usual.
I spent a fairly large number of minutes trying to understand this and... I failed. AFAIK the IPC type is a build-time decision so I don't understand how tests can "target" one IPC type in particular. I admit I never used the testbench.
I had a look at thesofproject/sof#9025 but there is very little CMake changes and there is a [DO NOT REVIEW] label for now. BTW: this has nothing to do with sof-test but I guess it's more convenient to have all "coverage gaps" in the same place. |
This needs to wait for #9025 to restore IPC3 testbench features (removed in current draft). There should be build for testbench3 and testbench4 and update to sof-test to run both. |
I don't think sof-test runs the testbench or that it ever has been? AFAIK there is only some github action compiling it with the Zephyr SDK. Is there anything else? |
There's scripts/host-testbench.sh run, yep it's not from sof-test but some action. |
Testbench can be built with support for ipc3 or ipc4, but not both. Testbench needs current tests to target IPC3 build only to allow upstreaming of ipc4 testbench (which can then reuse existing tests with changes for ipc4).
@singalsu @ranj063 fyi.
@marc-hb this is needed for v2.10, I think you may also need to help with all the cmake changes to build both flavours of testbench too. Thanks !
The text was updated successfully, but these errors were encountered: