Skip to content
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

[WIP] Tast: Set test priorities #896

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

denisyuji
Copy link
Contributor

This patch set aims to:

  • Add frequency limit for v4l2 video decoder tests as per Google's priority assignment.
  • Re-enable video.ChromeStackDecoder* tests, since kernelci now has the frequency feature to limit the times the tests will be executed
  • Split video.ChromeStackDecoder.* and video.ChromeStackDecoderVerification.* tests to have better granularity control of the video.ChromeStackDecoder* tests.

@denisyuji denisyuji force-pushed the tast-set-priorities branch 2 times, most recently from e99b379 to b4e58c5 Compare November 19, 2024 03:24
…rification.* tests

Split video.ChromeStackDecoder.* and
video.ChromeStackDecoderVerification.* tests in order to assign
different priorities (frequency) for these tests

Signed-off-by: Denis Yuji Shimizu <[email protected]>
…rification.* tests

Split video.ChromeStackDecoder.* and
video.ChromeStackDecoderVerification.* tests in order to assign
different priorities (frequency) for these tests

Signed-off-by: Denis Yuji Shimizu <[email protected]>
Re-enable video.ChromeStackDecoder* tests, since kernelci
now has the `frequency` feature to limit the times the
tests will be executed

Signed-off-by: Denis Yuji Shimizu <[email protected]>
Add frequency limit for v4l2 video decoder tests as per Google's
priority assignment.

Signed-off-by: Denis Yuji Shimizu <[email protected]>
@denisyuji denisyuji changed the title Tast: Set test priorities [WIP] Tast: Set test priorities Nov 26, 2024
@nuclearcat
Copy link
Member

If it is WIP - better to set draft status, then it wont be merged for sure, but still tested on staging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants