Confirmed users
3,376
edits
Buildbot/Talos/Sheriffing: Difference between revisions
m
→Overview: - update June 2016
(Moved microbench to https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/GTest#Sheriffing_policy) |
m (→Overview: - update June 2016) |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
The sheriff team does a great job of finding regressions in unittests and getting fixes for them or backing stuff out. This keeps our trees green and usable while thousands of checkins a month take place! | The code sheriff team does a great job of finding regressions in unittests and getting fixes for them or backing stuff out. This keeps our trees green and usable while thousands of checkins a month take place! | ||
For talos, we run about | For talos, we run about 85 jobs per push (out of ~1500+ total test jobs) to measure the performance of desktop builds. These jobs are green and the code sheriffs have little to do. | ||
Enter the role of a Performance Sheriff. This role looks at the data produced by these test jobs and finds regressions, root causes and gets bugs on file to track all issues and make interested parties aware of what is going on. | Enter the role of a Performance Sheriff. This role looks at the data produced by these test jobs and finds regressions, root causes and gets bugs on file to track all issues and make interested parties aware of what is going on. | ||