On Fri, Jul 25, 2025 at 11:37:13AM -0700, dan.j.williams@xxxxxxxxx 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@xxxxxxxxxxxxxx/ 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:
signature.asc
Description: PGP signature
