With respect to this ticket (as there is a need for unique-but-meaningfull identifier of the test), we had a discussion about naming the tests/tasks for Taskotron.
For the package-specific tests, we feel, that going by name {package_name}.{test_name} is the best, since we will (probably) look inside the package repo, to search for specific directory (?) with taskotron tests.
{package_name}.{test_name}
For generic tests, going with {fas_username}.{test_name} feels right, as we will (probably) somehow be registering new tests, so we can add (as a part of metadata) the FAS account of the responsible test (git repo) owner.
{fas_username}.{test_name}
Also - we should add the test name into the runner's envdata (if we go in the {package_name}/{fas_username}. scheme.
{package_name}/{fas_username}.
Setting low priority, this should be necessary to deal with only when we have third-party checks, I assume.
This is now obsolete, we mostly use dist. prefix for generic tasks and we don't attempt to run distgit tasks anymore.
dist.
Metadata Update from @kparal: - Issue close_status updated to: Invalid
Log in to comment on this ticket.