From [2021-04-20 EP Team meeting](https://docs.google.com/document/d/1yzHuosvykzb_kaldjGP9I6wxpNpMXdNEvEFBkHyZpXs/edit#bookmark=id.6jo5t4fefkda) we want to focus in Q2 on reducing the impact that flaky specs cause to pipeline stability that affect productivity of the Engineering team ## Benefits - Improve productivity - MR merge time - less retries needed during MWPS - Master stability improvement without manual action - Removes doubts on whether master is broken or not and default action of retry. - Defining acceptable thresholds for action like quarantining/focus on refactoring. - Step towards unlocking merge train ## Questions - What are some of the actions that should be taken based on this information? - What data is needed to deterministically take those actions? - How should data be gathered/stored to ensure actionability can be automated?