Performance/Tools/FAQ: Difference between revisions

(Created page with "{{DISPLAYTITLE:Performance Tools FAQ}} {{DISPLAYTITLE:Performance Tools FAQ}} = What is Perfherder? = [https://treeherder.mozilla.org/perf.html#/graphs Perfherder] is a tool...")
 
 
Line 301: Line 301:
# hg checkout abcde3
# hg checkout abcde3
## let's assume that build abcde4 broke the tests. you need to back it out in order to get the values of your investigated test on try:
## let's assume that build abcde4 broke the tests. you need to back it out in order to get the values of your investigated test on try:
### hg oops -r abcde4
### hg backout -r abcde4
## ./mach try fuzzy --full -q=^investigated-test-signature -m=abcde4_alert_###### (the baseline keyword is included just in the reference push message)
## ./mach try fuzzy --full -q=^investigated-test-signature -m=abcde4_alert_###### (the baseline keyword is included just in the reference push message)
## Use the [https://treeherder.mozilla.org/perf.html#/comparechooser| comparechooser] to compare between the 2 pushes.
## Use the [https://treeherder.mozilla.org/perf.html#/comparechooser| comparechooser] to compare between the 2 pushes.
# If the try values between abcde5 and abcde3 don't include the delta, then you'll know that abcde1 or abcde2 are suspects so you need to repeat the step you did for abcde3 to find out.
# If the try values between abcde5 and abcde3 don't include the delta, then you'll know that abcde1 or abcde2 are suspects so you need to repeat the step you did for abcde3 to find out.
342

edits