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

Refactoring for kselftest handling in pipeline #988

Merged
merged 2 commits into from
Feb 5, 2025

Conversation

broonie
Copy link
Member

@broonie broonie commented Jan 31, 2025

This is a minor refactoring of the base kselftest stuff in the pipeline,
in preparation for enabling more kselftests.

  • config/pipeline.yaml: Factor generic kselftest rules into a separate block
  • config/pipeline.yaml: Cover kselftest on -next by default

@broonie broonie force-pushed the kselftest-base branch 2 times, most recently from f09fe9a to 9d18b95 Compare January 31, 2025 14:46
config/pipeline.yaml Show resolved Hide resolved
@nuclearcat
Copy link
Member

Please rebase also

…block

Rather than using whatever the first kselftest in the pipeline config is
as the template let's define something that's just a template with a name
picked to sort before any actual kselftest. This reduces the churn when we
add suites with names that sort early and helps keep the configuration that
is generic distinct from that for whatever the first suite is.

Signed-off-by: Mark Brown <broonie@kernel.org>
Since -next is where the currently active upstream development is it's one
of the more important suites to cover, add it as a default for kselftest.

Now that the legacy system is disabled we have a lot more bandwidth in the
labs so there should be less concern about this than there was during the
bringup of the pipeline.

Signed-off-by: Mark Brown <broonie@kernel.org>
@nuclearcat nuclearcat added this pull request to the merge queue Feb 5, 2025
Merged via the queue into kernelci:main with commit 3ffd5e7 Feb 5, 2025
3 checks passed
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