Yeah, it looks like the "after" regression in the alert here is https://hg.mozilla.org/integration/autoland/rev/653d00ce1d0f45e9ff5b812cb783df0216e6ffb5 which is where we backed out bug 1850834. So we landed bug 1850834 and briefly got an improvement on this subtest, and then had to back it out (losing the improvement, i.e. regressing), and then since then we re-landed and got the improvement back.
Bug 1901213 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Yeah, it looks like the "after" regression in the alert here is https://hg.mozilla.org/integration/autoland/rev/653d00ce1d0f45e9ff5b812cb783df0216e6ffb5 which is where we backed out bug 1850834. So what happened is: we landed bug 1850834, and briefly got an improvement on this subtest, and then had to back it out (losing the improvement, i.e. regressing), and then since then we re-landed and got the improvement back.
Yeah, it looks like the "after" regression in the alert here is https://hg.mozilla.org/integration/autoland/rev/653d00ce1d0f45e9ff5b812cb783df0216e6ffb5 which is where we backed out bug 1850834. So what happened is: we landed bug 1850834, and briefly got an improvement on this subtest, and then had to back it out (losing the improvement, i.e. regressing), and that spawned this bug. And then later, we re-landed and got the improvement back.
Yeah, it looks like the "after" regression in the alert here is https://hg.mozilla.org/integration/autoland/rev/653d00ce1d0f45e9ff5b812cb783df0216e6ffb5 which is where we backed out bug 1850834. So what happened is: we landed bug 1850834, and briefly got an improvement on this subtest, and then had to back it out (losing the improvement, i.e. regressing), and that spawned this perf alert & resulted in this bug. And then later, we re-landed and got the improvement back.
Yeah, it looks like the "after" regression in the alert here is https://hg.mozilla.org/integration/autoland/rev/653d00ce1d0f45e9ff5b812cb783df0216e6ffb5 which is where we backed out bug 1850834. So what happened is: we landed bug 1850834, and briefly got an improvement on this subtest, and then had to back it out (losing the improvement, i.e. regressing), and that spawned this perf alert & resulted in this bug. And then later, we re-landed and got the improvement back (see bug 1850834 comment 39).