Hi :stransky, This performance regression was caused by bug 1852918, which bug was created because in bug 1852724 the title bar was not being displayed. I think bug 1852724's changes, which resulted in the title bar not being displayed it artificially improved the score and as a result of fixing the bug returned our score back to where it was before, which is why the improvements and regressions of 1852724 and 1852918 are inverses of each other I am going to close this bug and re-classify the alerts, I am going to close this bug and I apologize for all the confusion this has caused
Bug 1853972 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hi :stransky, This performance regression was caused by bug 1852918, which was created because in bug 1852724 the title bar was not being displayed. I think bug 1852724's changes, which resulted in the title bar not being displayed it artificially improved the score and as a result of fixing the bug returned our score back to where it was before, which is why the improvements and regressions of 1852724 and 1852918 are inverses of each other I am going to close this bug and re-classify the alerts, I am going to close this bug and I apologize for all the confusion this has caused
Hi :stransky, This performance regression was caused by bug 1852918, which was created because in bug 1852724 the title bar was not being displayed. I think bug 1852724's changes, which resulted in the title bar not being displayed it artificially improved the score and as a result of fixing the bug returned our score back to where it was before, which is why the improvements and regressions of 1852724 and 1852918 are inverses of each other I am going to close this bug and re-classify the alerts, I am going to close this bug and I apologize for all the confusion this has caused Generally when we have a fix for a test fail it results in a backout and is clearly identifiable in the commit message and treeherder logs but this was not the case in this bug, but now that we know this can happen I will incorporate it into our perf-sheriffing workflow to not have the same confusion arise again