-
Notifications
You must be signed in to change notification settings - Fork 45
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
[SKIP CI] run-all-test: make similar test cases with pr test #1019
base: main
Are you sure you want to change the base?
Conversation
run-all-test.h provides a good way to do local sanity tests. This change is to accommodate a known pr test plan. +kernel-boot-log +playback_all_formats +capture_all_formats +runtime-pm-status +multiple-pipeline-all -volume -xrun-injection-playback -xrun-injection-capture Signed-off-by: Fred Oh <fred.oh@linux.intel.com>
Is it too late to switch the underscores to dashes in the file names, to match the formatting everywhere else? |
@@ -169,6 +171,10 @@ interrupted_results() | |||
exit 1 | |||
} | |||
|
|||
test_kernel-boot-log() |
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.
I agree with @greg-intel , please no mix in the same name.
test_kernel-boot-log() | |
test_kernel_boot_log() |
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.
I'm leaning towards renaming the few tests that have underscores to be dashes, as 95% of our tests are named using dashes. I'm not sure how the underscore tests got through, I don't remember seeing them...
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.
I'm leaning towards renaming the few tests...
Consistency and simplicity are good and should absolutely be a goal for new code or code that is changing anyway for other reasons.
For unchanged code it's much more questionable. Is it worth the git churn and potential git conflicts with PRs in progress, branches, etc? It depends.
run-all-tests.sh provides a good way to do local sanity tests. This change is to accommodate a known pr test plan.
+kernel-boot-log
+playback_all_formats
+capture_all_formats
+runtime-pm-status
+multiple-pipeline-all
-volume
-xrun-injection-playback
-xrun-injection-capture
I put 'SKIP CI', run-all-test.sh is not part of device test.