workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: dan.j.williams@intel.com
Cc: Jakub Kicinski <kuba@kernel.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
	Donald Zickus <dzickus@redhat.com>,
	Gustavo Padovan <gustavo.padovan@collabora.com>
Subject: Re: Crediting test authors
Date: Sat, 26 Jul 2025 22:44:29 +0100	[thread overview]
Message-ID: <aIVMPbZcmAvG9z2o@finisterre.sirena.org.uk> (raw)
In-Reply-To: <6883ced97d944_134cc7100fa@dwillia2-xfh.jf.intel.com.notmuch>

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

On Fri, Jul 25, 2025 at 11:37:13AM -0700, dan.j.williams@intel.com wrote:
> Jakub Kicinski wrote:

> > So a tag would be ideal. But it's a hard nut to crack. Best I can come
> > up with would be:

> > Reproducer: test.case.path # 001122aabb (optimal) commit of the test case

> That's true, more than a few times I have had distro folks reach out to
> ask "how do I verify this backport" and end up manually pointing to the
> new unit test that backstops a fix.

> Although, from that tag I would not know where to get the commit. Maybe:
> 
> Test: <git url>
> 
> ...as a new Link: type?

It seems like there's some overlap here with the work that people have
been intermittently trying to do on test cataloging, eg:

   https://lore.kernel.org/workflows/CAK18DXYitS7hL1mA3QsPLmW9-R0q6Kin0C5Uv9fj=uS90WSnxA@mail.gmail.com/

That's been approached more from the "what tests should I run?" end of
things since it's been driven by people interested in testing and CI,
but it feels like there's a lot of overlap with the describing the
suites part of things.  It'd be a lot easier to write and read tags like
the above if we could define some more compact names than git URLs for
suites/tests.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-07-26 21:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25 15:00 Jakub Kicinski
2025-07-25 15:26 ` Theodore Ts'o
2025-07-25 16:38 ` dan.j.williams
2025-07-25 17:20   ` Jakub Kicinski
2025-07-25 17:20     ` Jakub Kicinski
2025-07-25 18:37     ` dan.j.williams
2025-07-26 21:44       ` Mark Brown [this message]
2025-07-31 14:30         ` Gustavo Padovan
2025-07-25 16:39 ` Mark Brown
2025-07-25 17:15   ` Jakub Kicinski

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=aIVMPbZcmAvG9z2o@finisterre.sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dzickus@redhat.com \
    --cc=gustavo.padovan@collabora.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=workflows@vger.kernel.org \
    /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