Confirmed users
90
edits
Firefox OS/Performance/Datazilla: Difference between revisions
→Triaging Regressions
Kevingrandon (talk | contribs) No edit summary |
Kevingrandon (talk | contribs) |
||
| Line 15: | Line 15: | ||
== Triaging Regressions == | == Triaging Regressions == | ||
Each point in datazilla has a gaia, gecko, and platform build revision id. You can use this information to triage and locate where the regression occurred. One way of doing this is to use the B2G profiler: https://github.com/mozilla-b2g/B2G/blob/master/profile.sh | Each point in datazilla has a gaia, gecko, and platform build revision id. You can use this information to triage and locate where the regression occurred. | ||
=== Profiling === | |||
One way of doing this is to use the B2G profiler: https://github.com/mozilla-b2g/B2G/blob/master/profile.sh | |||
=== Git Bisect === | |||
You can use git bisect to narrow down the range between two datapoints. This is useful for finding offending gaia commits. You can select two adjacent ranges and git bisect from one to another. Git bisect tutorial: http://webchick.net/node/99 | |||
== Resources == | == Resources == | ||