Wonder if autoland's backout rate will go up when autoland is detached from
mozreview (letting someone autoland directly from bugzilla is in the plans,
I believe).

On Tue, Mar 7, 2017 at 4:47 AM, Carsten Book <cb...@mozilla.com> wrote:

> Hi,
>
> i agree with Sebastian - the integration of submitting to try and getting
> the results in mozreview helps i think a lot.
>
> Also this is all great feedback and will add a more detailed area about
> backouts (where they happen like inbound/autoland, and reason) in the next
> sheriff monthly report.
>
> Cheers,
> - Tomcat
>
> On Tue, Mar 7, 2017 at 1:27 PM, Sebastian Hengst <a...@gmx.de> wrote:
>
>> Mozreview shows the results of Try pushes (if they have been requested)
>> near the top where also the landing can be requested which makes it less
>> likely that issues get missed (pushing to Try and not checking the results
>> is not that rare).
>>
>> Mozreview is also the only repository to which the person who gets backed
>> out the most (my subjection impression) pushes to (doesn't mean the second
>> push will stick).
>>
>> Inbound is also often used for platform-wide changes which might have
>> bitrotted between the Try push and the push to inbound.
>>
>> Sebastian
>>
>> -------- Original-Nachricht --------
>> Betreff: Re: [Sheriffs] Sheriff Highlights and Summary in February 2017
>> Von: David Burns <dbu...@mozilla.com>
>> Datum: 2017-03-07 12:23
>>
>>> One thing that we have also noticed is that the backout rate on autoland
>>> is lower than inbound.
>>>
>>> In the last 7 days backout rate is averaging (merges have been removed):
>>>
>>>   * Autoland 6%.(24 backouts out of 381 pushes)
>>>   * Inbound 12% (30 backouts out of 251 pushes)
>>>
>>> I don't have graphs to show this but when I look at
>>> https://futurama.theautomatedtester.co.uk/ <
>>> https://futurama.theautomatedtester.co.uk/>   each week I have seen
>>> this result consistenly for about a month.
>>>
>>> David
>>>
>>>
>>>
>>> On 7 March 2017 at 09:03, Carsten Book <cb...@mozilla.com <mailto:
>>> cb...@mozilla.com>> wrote:
>>>
>>>     Hi Lawrence,
>>>
>>>     most (i would say 95 %) of the backouts are for Code issues - this
>>>     include bustages and test failures.
>>>
>>>      From this Code Issues i would guess its about 2/3 for breaking
>>>     tests and 1/3 Build Bustages.
>>>
>>>     The other backout reasons are merge conflicts / backout requests for
>>>     changes causes new regressions out of our test suites / backout
>>>     requests from developers etc -
>>>
>>>     In February the backout rate was (excluding the servo merge with
>>>     8315 changesets from the 13242) = 297 in 4927 changesets = ~ 6 %
>>>     In January the backout rate = 302 backouts in 4121 changesets = 7 %
>>>
>>>     We had a much higher backout rate in the past i think - so it
>>>     stabilized now with this 6-7 % backout rate in the last months,
>>>
>>>     If you think its useful, i can provide for the next monthly report a
>>>     more detailed analysis like x % =  backouts because builds bustages,
>>>     y %= backouts for test failures etc .
>>>
>>>     Cheers,
>>>       -Tomcat
>>>
>>>
>>>     On Mon, Mar 6, 2017 at 11:13 PM, Lawrence Mandel
>>>     <lman...@mozilla.com <mailto:lman...@mozilla.com>> wrote:
>>>
>>>         Hi Tomcat,
>>>
>>>         Do you have any more details about the reasons why the 297
>>>         changesets needed to be backed out?
>>>
>>>         Thanks,
>>>
>>>         Lawrence
>>>
>>>         On Wed, Mar 1, 2017 at 6:05 AM, Carsten Book <cb...@mozilla.com
>>>         <mailto:cb...@mozilla.com>> wrote:
>>>
>>>             Hi,
>>>
>>>             We will be more active in 2017 and inform more about whats
>>>             happening in Sheriffing and since its already March.... :)
>>>
>>>             In February we had about 13242 changesets landed on
>>>             mozilla-central monitored by Sheriffs.
>>>
>>>             (The high number of changes is because of the merge from
>>>             servo to mozilla-central with about 8315 changesets).
>>>
>>>             297 changesets were backed out in February.
>>>
>>>             Beside this Sheriffs took park in doing uplifts and
>>>             checkin-needed bugs.
>>>
>>>             The Current Orangefactor is 10.43 (7250 test failures
>>>             failures in 695 pushes in the last 7 days).
>>>             You can find the list of top Intermittent failure bugs here
>>>             https://brasstacks.mozilla.com/orangefactor/
>>>             <https://brasstacks.mozilla.com/orangefactor/>
>>>
>>>             You can find more statistics here:
>>>             https://futurama.theautomatedtester.co.uk/
>>>             <https://futurama.theautomatedtester.co.uk/>
>>>
>>>             A big thanks to the Team especially our Community Sheriffs
>>>             for handling the new Tier 2 Stylo Build on integration
>>>             trees  and mozilla-central  and the teamwork with the
>>>             Developers!
>>>
>>>             If you want also to be a Community Sheriffs, as part of more
>>>             blogging about Sheriffing i published a blog post about it :
>>>             https://blog.mozilla.org/tomcat/2017/02/27/community-sheriff
>>> s/
>>>             <https://blog.mozilla.org/tomcat/2017/02/27/community-sherif
>>> fs/>
>>>
>>>             Let us know when you have any Question or Feedback about
>>>             Sheriffing.
>>>
>>>             Cheers,
>>>               -Tomcat
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Sheriffs mailing list
>>> sheri...@mozilla.org
>>> https://mail.mozilla.org/listinfo/sheriffs
>>>
>>>
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to