Skip to content

Conversation

@fredoh9
Copy link
Contributor

@fredoh9 fredoh9 commented Apr 7, 2023

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.

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>
@fredoh9 fredoh9 requested a review from a team as a code owner April 7, 2023 06:23
@marc-hb marc-hb requested review from bardliao and plbossart April 9, 2023 23:59
@greg-intel
Copy link
Contributor

Is it too late to switch the underscores to dashes in the file names, to match the formatting everywhere else?

@marc-hb marc-hb added the type:enhancement New framework feature or request label Jul 12, 2023
exit 1
}

test_kernel-boot-log()
Copy link
Collaborator

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.

Suggested change
test_kernel-boot-log()
test_kernel_boot_log()

Copy link
Contributor

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...

Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:enhancement New framework feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants