From: Scott Mayhew <smayhew@redhat.com>
To: kdevops@lists.linux.dev
Subject: Re: [PATCH 0/9] tweak results organization and reporting
Date: Tue, 4 Mar 2025 20:11:32 -0500 [thread overview]
Message-ID: <Z8ekxGKhdB1vWYDv@aion> (raw)
In-Reply-To: <20250305005755.697599-1-smayhew@redhat.com>
Whoops, I accidentally re-sent this series while I was sending the
"Don't include the codereadyrepo role if we're using a custom yum repofile"
patch.
Sorry for the noise.
-Scott
On Tue, 04 Mar 2025, Scott Mayhew wrote:
> I do most of my kdevops runs under buildbot. Currently I don't have an
> easy way to view test results in buildbot's web interface.
>
> The first four patches implement a "last-run" directory and
> "last-kernel.txt" file similar to what the fstests workflow already has.
> This is mainly to facilitate the remaining patches, but I think it will
> also make it easier for me to feed my test results into other tooling in
> the future.
>
> The remaining patches add a "<workflow>-show-results" makefile target,
> which basically print the test results to the standard output. The
> results for the most recent run are printed by default, but that can be
> changed by overriding the LAST_KERNEL variable. The results printed
> varies from workflow to workflow, and can be overidden via the PATTERN
> variable.
>
> Scott Mayhew (9):
> pynfs: add last-run directory and last-kernel.txt to the results
> nfstest: add last-run directory and last-kernel.txt to the results
> gitr: add last-run directory and last-kernel.txt to the results
> ltp: add last-run directory and last-kernel.txt to the results
> fstests: add makefile target to show test results
> pynfs: add makefile target to show test results
> nfstest: add makefile target to show test results
> gitr: add makefile target to show test results
> ltp: add makefile target to show test results
>
> playbooks/roles/gitr/tasks/main.yml | 59 +++++++++++++++++++++----
> playbooks/roles/ltp/tasks/main.yml | 60 ++++++++++++++++++++++++--
> playbooks/roles/nfstest/tasks/main.yml | 60 ++++++++++++++++++++++----
> playbooks/roles/pynfs/tasks/main.yml | 38 +++++++++++++++-
> workflows/fstests/Makefile | 16 +++++++
> workflows/gitr/Makefile | 21 +++++++++
> workflows/ltp/Makefile | 21 +++++++++
> workflows/nfstest/Makefile | 17 ++++++++
> workflows/pynfs/Makefile | 12 ++++++
> 9 files changed, 282 insertions(+), 22 deletions(-)
>
> --
> 2.48.1
>
>
next prev parent reply other threads:[~2025-03-05 1:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 0:57 [PATCH 0/9] tweak results organization and reporting Scott Mayhew
2025-03-05 0:57 ` [PATCH] Don't include the codereadyrepo role if we're using a custom yum repofile Scott Mayhew
2025-03-05 0:57 ` [PATCH 1/9] pynfs: add last-run directory and last-kernel.txt to the results Scott Mayhew
2025-03-05 0:57 ` [PATCH 2/9] nfstest: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 3/9] gitr: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 4/9] ltp: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 5/9] fstests: add makefile target to show test results Scott Mayhew
2025-03-05 0:57 ` [PATCH 6/9] pynfs: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 7/9] nfstest: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 8/9] gitr: " Scott Mayhew
2025-03-05 0:57 ` [PATCH 9/9] ltp: " Scott Mayhew
2025-03-05 0:57 ` [PATCH] Don't include the codereadyrepo role if we're using a custom yum repofile Scott Mayhew
2025-03-05 1:11 ` Scott Mayhew [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-03 13:09 [PATCH 0/9] tweak results organization and reporting Scott Mayhew
2025-03-12 20:09 ` Chuck Lever
2025-03-12 22:58 ` Luis Chamberlain
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=Z8ekxGKhdB1vWYDv@aion \
--to=smayhew@redhat.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