Add API to Treeherder which allows setting new_failure=True
Categories
(Tree Management :: Treeherder: API, enhancement)
Tracking
(Not tracked)
People
(Reporter: jmaher, Unassigned)
Details
this feature request is sort of a hack, but it serves a purpose. In the future world of "auto classification" we could be overzealous on secondary revisions for a new failure and flag those as intermittent. Of course the new_failure will be properly classified and visible for investigation into if this is a regression or not. The theory here is if it is determined to be a regression, we want to find all similar errors in a range of pushes that match the new_failure and adjust those to be classified as fixed_by_commit and set new_failure=True. This bug is about providing a mechanism for setting new_failure=True.
The main driver for this is then we can have properly annotated metadata for tasks and failure lines- resulting in the ability to do a sql query (feeding a dashboard) to determine all of the tasks that found a regression that are not marked as new_failure. Essentially this is a cleanup for consistent data for the sole purpose of making the dashboard consistent.
Currently new_failure is a flag set on text_log_error entries.
This API would:
- take input of a list of jobids
- take input of a branch (default 'autoland' - which is all that would be supported at first)
- take input of the failure message (probably better to use example jobid to find desired line)
- for all matching jobids that have the failure, update the text_log_error.new_failure=True
- output would be "ok" || "failure message"
Description
•