Generalize heatmap logic and add support for flakiness
What does this MR do and why?
This adds a heatmap table for failureflaky-test issues ( flakiness1, flakiness2, flakiness3, flakiness4) quarantined (quarantine) and not quarantined.
Expected impact & dry-runs
Example of an actual heatmap for the groupsource code generated from the upcoming updated triage-ops
implementation (links are all functional
flakiness1 | flakiness2 | flakiness3 | flakiness4 | No flakiness status | |
---|---|---|---|---|---|
No quarantined | 2 | 1 | 43 | 392 | 18 |
quarantine | 1 | - | - | - | 2 |
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-
Closes #1506 (closed)
Edited by Rémy Coutable