flake-stats: create overview page to ease browsing of history

[dhiller]

TL;DR

goal: write a go tool that generates an overview page for the flake-stats reports and add it to the set of go commands located in robots/cmd folder in kubevirt/project-infra repository.

Task: create a flake-stats-overview.html

We use the flake-stats tool to generate an overview of how we are doing wrt flakes in k/kubevirt

This tool generates a daily overview here.

We want to generate a landing page that links directly to each of the reports for the last, say 90 days. Or even more, we wouldn't really care whether the actual report exists.

This i.e. would integrate the individual flake-stats reports into a new flake-stats-overview.html. For easier browsing this should group the entries and display them newest first.

Grouping could be done monthly or week-wise.

Extra sugar would be some sort of logical arrangement that helps the user to find the report he wants quickly. I.e. a calendar view.

Background

All flake-stats pages are accessible from google cloud storage and browseable via http:

$ gsutil ls gs://kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/ | grep flake-stats
gs://kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days-2023-07-19.html
gs://kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days-2023-07-20.html
gs://kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days-2023-07-21.html
...
gs://kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days-2023-08-13.html
gs://kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days-2023-08-14.html
gs://kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days-2023-08-15.html
gs://kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days.html

Note: last line shows the latest report

[dhiller]

/assign

[kubevirt-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[dhiller]

/remove-lifecycle stale

[kubevirt-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[dhiller]

/remove-lifecycle stale

[dhiller]

/good-first-issue

[kubevirt-bot]

@dhiller: This request has been marked as suitable for new contributors.

Guidelines

• No Barrier to Entry
• Clear Task
• Solution Explained
• Provides Context
• Identifies Relevant Code
• Gives Examples
• Ready to Test
• Goldilocks priority
• Up-To-Date

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to [this](https://github.com/kubevirt/project-infra/issues/2935): >/good-first-issue Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[dhiller]

/unassign

[dhiller]

/type enhancement /area flakefinder /area automation

[dhiller]

/kind enhancement

[kubevirt-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/project-infra/issues/2935#issuecomment-2269256221): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[dhiller]

/remove-lifecycle rotten /lifecycle frozen /reopen

[kubevirt-bot]

@dhiller: Reopened this issue.

In response to [this](https://github.com/kubevirt/project-infra/issues/2935#issuecomment-2302004438): >/remove-lifecycle rotten >/lifecycle frozen >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[anishbista60]

@dhiller can i work here ?

[dhiller]

@dhiller can i work here ?

Sure, just go ahead.