-
Notifications
You must be signed in to change notification settings - Fork 59
check_alsabat.sh: add format support #1009
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
Conversation
marc-hb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is hiding a backwards-incompatible change. I understand you did that to align with alsabat which is good but it will break existing users. This should at the very least be explained in a separate commit message, clearly visible in the git log.
- commit 1: rename -f[requency] option to -F for alsabat consistency
- commit 2: add new -f[format] option
With the NEW code, what happens when someone does check-alsabat.sh -f 821? Do they get a meaningful error message from alsabat? Add that error message in the first commit message.
test-case/check-alsabat.sh
Outdated
|
|
||
| OPT_NAME['r']='rate' OPT_DESC['r']='sample rate' | ||
| OPT_HAS_ARG['r']=1 OPT_VAL['r']=48000 | ||
| OPT_HAS_ARG['r']=1 OPT_VAL['r']=48000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is pure git noise, don't.
https://wiki.openstack.org/wiki/GitCommitMessages#Structural_split_of_changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
482481b to
3783bca
Compare
| OPT_NAME['f']='format' OPT_DESC['f']='target format' | ||
| OPT_HAS_ARG['f']=1 OPT_VAL['f']="S16_LE" | ||
|
|
||
| OPT_NAME['F']='frequency' OPT_DESC['F']='target frequency' | ||
| OPT_HAS_ARG['F']=1 OPT_VAL['F']=821 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will the change of -f break the backward compatibility? For example, daily MTL test runs for different frequencies with -f.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, so we need to update the alsabat test config in web accordingly when merging this PR.
|
Very small conflict with #991 that I just merged, need to rebase sorry. One model missing and some suspend/resume failures in https://sof-ci.01.org/softestpr/PR1009/build173/devicetest/index.html https://sof-ci.01.org/softestpr/PR1009/build174/devicetest/index.html all green. |
…tency Signed-off-by: Keqiao Zhang <keqiao.zhang@intel.com>
add a new option -f to support different formats in alsabat test. Signed-off-by: Keqiao Zhang <keqiao.zhang@intel.com>
3783bca to
53328bf
Compare
|
@marc-hb , rebased. Please give a check again. if no problems, I will merge it today. |
marc-hb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make sure the test results are OK-ish.

add a -f option to support audio format.