Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define an L1 key for reporting of subresults #3515

Open
happz opened this issue Feb 7, 2025 · 0 comments
Open

Define an L1 key for reporting of subresults #3515

happz opened this issue Feb 7, 2025 · 0 comments
Labels
specification Metadata specification (core, tests, plans, stories) step | report Stuff related to the report step

Comments

@happz
Copy link
Collaborator

happz commented Feb 7, 2025

See #3331 (comment)

As discussed, reporting - or not reporting - subresults seems to be very useful when controlled per-test. tmt does not have such a key. When enabled, report plugins would follow it when reporting results. An idea of plugin-owned keys is not necessary, we felt the use case of plugin-agnostic key to control the reporting per-test is strong enough.
@happz happz added specification Metadata specification (core, tests, plans, stories) step | report Stuff related to the report step labels Feb 7, 2025
@happz happz mentioned this issue Feb 7, 2025
Open
14 tasks
@happz happz changed the title Define a key for reporting of subresults Define an L1 key for reporting of subresults Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
specification Metadata specification (core, tests, plans, stories) step | report Stuff related to the report step
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@happz