Fix test bench scripts#2785
Conversation
add status check for the host testbench also fix file size check Signed-off-by: Pan Xiuli <xiuli.pan@linux.intel.com>
After fix the host-testbench.sh issues, re-enable the testbench test in Travis. Signed-off-by: Pan Xiuli <xiuli.pan@linux.intel.com>
|
@singalsu It seems we got vol host test bench failed |
|
Strange, I'm able to run volume component tests this way: The verdict is fail due to volume ramp no getting scheduled and resulting wrong gain vs. expected but the data flow is OK. Though I have not rebased today. Is your testbench binary up-to-date? |
lgirdwood
left a comment
There was a problem hiding this comment.
Code looks fine to me, I assume you are saying here that script is now correctly detecting a testbench failure.
|
@xiulipan @lgirdwood I had the testbench up-to-date but used old test topologies, maybe two weeks old. After I re-ran today "scripts/build-tools.sh -t" the testbench volume topology parsing failed. I'll start to debug what has happened. Thanks for reporting this! |
|
SOFCI TEST |
|
The volume volume topology parsing fix is in #2824. I'd assume the PR is in quite good shape now after some review rounds. |
|
SOFCI TEST |
|
Why are we waiting to merge #2824 and this? |
|
@singalsu can you check the CI output, I'll run it again. |
|
SOFCI TEST |
|
@lgirdwood The fails above look unrelated. I tested it also locally. With git master from today and this patch applied this run passes now: |
|
@lgirdwood @singalsu I re trigger the Travis test check if the testbench can work now. |
|
@xiulipan looks like the CI version of xtensa-buildall.sh is missing some machines from the build. It's an unrelated failure. Jenkins is usual issues. |
|
@lgirdwood What is missed here? I do not see any issue in |
|
@xiulipan it could be a stale result. I've seen this before. |
Add status check and fix type size check.
re-enable the test bench check in Travis
fix #2752