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.

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

Conformance Profiles: summaries for profiles without content #2235

Closed
shaneutt opened this issue Jul 25, 2023 · 3 comments · Fixed by #2799
Closed

Conformance Profiles: summaries for profiles without content #2235

shaneutt opened this issue Jul 25, 2023 · 3 comments · Fixed by #2799
Assignees
Labels
area/conformance kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone

Comments

@shaneutt
Copy link
Member

shaneutt commented Jul 25, 2023

What happened:

In the last couple of PRs to document some conformance profile reports (#2192 , #2232) I noticed that the "summary" field is often empty for reports.

What you expected to happen:

At best, the tooling automates a human readable summary that clearly summarizes the results of the test.

At minimum, let's just not emit empty string fields when the field isn't being set.

@shaneutt shaneutt added kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. area/conformance labels Jul 25, 2023
@mlavacca
Copy link
Member

mlavacca commented Jul 25, 2023

You mentioned #2191 in the issue description, which does not seem relevant, probably a copy-paste error :)

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 25, 2024
@mlavacca
Copy link
Member

/remove-lifecycle stale
/assign

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 25, 2024
@shaneutt shaneutt added this to the v1.1 milestone Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/conformance kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants