Confirmed users
64
edits
Dev-sanity: Difference between revisions
Jump to navigation
Jump to search
→Automatic retrigger of oranges on try
Chmanchester (talk | contribs) |
Chmanchester (talk | contribs) |
||
| Line 24: | Line 24: | ||
== Automatic retrigger of oranges on try == | == Automatic retrigger of oranges on try == | ||
Retrigger failed jobs on try automatically. This is a pulse service that listens for failed test jobs and triggers each one two additional times. The idea is to reduce time spent determining whether a particular failure on try is an intermittent issue or a persistent failure introduced by a specific change. A common response to orange jobs on try is to retrigger them to determine if the failure persists, and although it results in more test jobs on try, the service is intended to save developer time by replacing this manual process with an automated one. | |||
A related feature implemented by this service is the ability to automatically build every test job on a push a certain number of times. This is a long-requested feature intended to be used by those investigating or proving a fix for an intermittent failures as well as those establishing a baseline for comparing Talos results across revisions. | |||
= Others? = | = Others? = | ||