From: "Theodore Ts'o" <tytso@mit.edu>
To: Jakub Kicinski <kuba@kernel.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: Crediting test authors
Date: Fri, 25 Jul 2025 11:26:58 -0400 [thread overview]
Message-ID: <20250725152658.GA236659@mit.edu> (raw)
In-Reply-To: <20250725080023.6425488c@kernel.org>
On Fri, Jul 25, 2025 at 08:00:23AM -0700, Jakub Kicinski wrote:
>
> Does anyone have ideas about crediting test authors or tests for bugs
> discovered? We increasingly see situations where someone adds a test
> then our subsystem CI uncovers a (1 in a 100 runs) bug using that test.
I just list the test that discovered the bug and which was cleared by
the commit, and assume that the test author will get credited in the
upstream test repository (e.g., such as generic/750 from fstests or
inotify02 from ltp). So it's not something that I've worried about.
I suppose if the test repository isn't as well known, or if the test
hasn't been checked anywhere at all, your concern that the test author
should be credited is something I can understand. But it hasn't come
up for me.
In other cases, if the commit hasn't been stable yet (say for kunit or
kselftests coming from some other tree), I'll just throw in a Link:
tag pointing at lore.kernel.org.
- Ted
next prev parent reply other threads:[~2025-07-25 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 15:00 Crediting test authors Jakub Kicinski
2025-07-25 15:26 ` Theodore Ts'o [this message]
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
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=20250725152658.GA236659@mit.edu \
--to=tytso@mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.