push health should use data as "NEW" failures only
Categories
(Tree Management :: Treeherder: Frontend, task)
Tracking
(Not tracked)
People
(Reporter: jmaher, Unassigned)
References
(Blocks 2 open bugs)
Details
currently push health is using a more comprehensive design to get raw failures as well as ignoring known intermittents. This is expensive in terms of CPU time and wall time. Since the original creation of push health, we have created "NEW" failures. If a failure is NEW (failure_classification_id=6), then we know it isn't a known intermittent (work is done to remove regressions from the list, as well as to sanitize the error lines).
With a potential upcoming step in log parser to take additional data (retriggers, confirm-failure, future pushes on integration branches) and compare results of the test group (or overall task) and determine if the failures are repeated or intermittent. If intermittent the task will have failure_classification_id=8, so a filter on failure_classification_id=6 will continue to update with accurate data.
There are other aspects of push health that will need updating (showing the similar tasks- maybe we don't need to?!?, if we do- add in confirm failures), when retriggering, use confirm-failure instead, we don't need multiple retriggers.
Upon resolution of this bug, please file a bug for the next logical step/work-item. That might be a UI update, database cleanup, refactor code, add/remove functionality, etc.
Description
•