coordination #152773
open
- Status changed from Workable to In Progress
- Subject changed from [epic] Provide relevant metrics for Yam squad to [epic] Provide relevant squad metrics
Had a quick look at the metabase chart. Nicely shows the pain points, but
- I see a count of failures, but I don't have any idea when the counting started. So let us assume that we fix the problems in
installation, then what will happen? Counter remains at 374? It would be really helpful if this would be a "counts for the last week" or "counts for the last 4 weeks" or whatever, so that after fixing issues the testsuite or module would go down in this list.
- This is a very global view, I'd love to have e.g. the entries that are our squad's responsibility highlighted in a different color.
rainerkoenig wrote in #note-5:
Had a quick look at the metabase chart. Nicely shows the pain points, but
- I see a count of failures, but I don't have any idea when the counting started. So let us assume that we fix the problems in
installation, then what will happen? Counter remains at 374? It would be really helpful if this would be a "counts for the last week" or "counts for the last 4 weeks" or whatever, so that after fixing issues the testsuite or module would go down in this list.
The specific metabase "question" https://metabase.mae.suse.de/question/318-which-testsuites-fail-the-most-on-osd has the filters "t_created Previous 30 Days" and "result is failed" so it's effectively what you called "counts for the last 4 weeks". Obviously this can be changed based on specific needs.
- This is a very global view, I'd love to have e.g. the entries that are our squad's responsibility highlighted in a different color.
You should be able to create specific queries in metabase yourself to suit your needs.
- Description updated (diff)
- Subtask deleted (
#157354)
Also available in: Atom
PDF