From: Chuck Lever III <chuck.lever@oracle.com>
To: "kdevops@lists.linux.dev" <kdevops@lists.linux.dev>
Subject: Re: [PATCH v2] workflows: Add an "ltp" workflow
Date: Fri, 22 Mar 2024 18:10:23 +0000 [thread overview]
Message-ID: <D85F2375-9E69-49D3-9562-354367A25C95@oracle.com> (raw)
In-Reply-To: <171095857841.999587.5630011881507554574.stgit@renoir.1015granger.net>
> On Mar 20, 2024, at 2:24 PM, Chuck Lever <cel@kernel.org> wrote:
>
> From: Chuck Lever <chuck.lever@oracle.com>
>
> LTP contains a number of file system-related tests, including the
> nfslock tests, the fs* tests, and the syscall/*notify tests. These
> tests have been a favorite of distributors' Q/A teams for many
> years, so it makes sense to include them to help file systems
> developers get in front of testing results that might be seen only
> after an upstream kernel release is prepared for a Linux
> distribution.
>
> LTP test subgroups are enabled by Kconfig options to avoid running
> tests that do not directly pertain to the developer's interests.
>
> In "dedicated" mode, a separate target node is brought up for each
> each test group, allowing multiple test groups to be run
> concurrently. This helps increase the number of tests that can be
> run in a given amount of elapsed time.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>
> Significant changes since RFC:
> - Non-dedicated mode tested and working
> - Expanded the patch description
> - Added a "cve" test group
> - Replaced install-deps with ansible.builtin.package
> - Replaced brute force set-up code with a list and a dictionary
> - 'copy_results' now grabs files under /opt/ltp/output/ too
Pushed to master.
--
Chuck Lever
prev parent reply other threads:[~2024-03-22 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 18:24 [PATCH v2] workflows: Add an "ltp" workflow Chuck Lever
2024-03-22 18:10 ` Chuck Lever III [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D85F2375-9E69-49D3-9562-354367A25C95@oracle.com \
--to=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).