From: Jakub Kicinski <kuba@kernel.org>
To: <dan.j.williams@intel.com>
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 10:20:19 -0700 [thread overview]
Message-ID: <20250725102019.7add0be0@kernel.org> (raw)
In-Reply-To: <6883b3046b640_134cc7100ad@dwillia2-xfh.jf.intel.com.notmuch>
On Fri, 25 Jul 2025 09:38:28 -0700 dan.j.williams@intel.com wrote:
> Jakub Kicinski wrote:
> > Hi!
> >
> > 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.
> >
> > Using reported-by doesn't feel right. But credit should go to the
> > person who wrote the test. Is anyone else having this dilemma?
>
> Is that not a "credit in the changelog" situation?
>
> "Big thanks to DeveloperX for their recent TestY added with CommitZ for
> catching this case."
That's what we do usually, but I'm a strong believer in (LWN) statistics
to help people justify the work they do upstream. Feels even more
important for testing than feature development in a way.
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
? Could potentially be useful for backporters?
> Reported-by: Some CI Bot
I guess we'd need something like:
Reported-by: subsystem CI # Person Who <developed@the.test> ?
next prev parent reply other threads:[~2025-07-25 17:20 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
2025-07-25 16:38 ` dan.j.williams
2025-07-25 17:20 ` Jakub Kicinski [this message]
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=20250725102019.7add0be0@kernel.org \
--to=kuba@kernel.org \
--cc=dan.j.williams@intel.com \
--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.