This bug is for running a new analysis to find high value tests/metrics, and see if there are any tests that we could disable or metrics that we should not alert on. In the past, we've used this code to determine "high-value" tests, not metrics specifically, but it could be modified to do either tests or metrics by changing up the query that we're using to get the data: https://github.com/mozilla/mozperftest-tools/blob/master/high-value-tests/generate_high_value_tests.py The query used: https://github.com/mozilla/mozperftest-tools/blob/master/high-value-tests/sql_query.txt The query wasn't fixed to work in postgresql, so it would need some fixes.
Bug 1960664 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This bug is for running a new analysis to find high value tests/metrics, and see if there are any tests that we could disable or metrics that we should not alert on. In the past, we've used this code to determine "high-value" tests, not metrics specifically, but it could be modified to do either tests or metrics by changing up the query that we're using to get the data: https://github.com/mozilla/mozperftest-tools/blob/master/high-value-tests/generate_high_value_tests.py The query used: https://github.com/mozilla/mozperftest-tools/blob/master/high-value-tests/sql_query.txt The query wasn't fixed to work in postgresql, so it would need some fixes. It also only looks at fixed by `backout` alerts, but we should see if we could use the `fixed` option as well.