Also sprach Andrew Halberstadt :
> I don't have any data to back this up, but my suspicion is that a
> large percentage of backouts had try runs, but said try runs
> didn't run the jobs that failed and caused the backout.
I ascribe to this explanation. This has happened to me a few times
because
On Friday, March 10, 2017 at 3:46:14 PM UTC-5, Kris Maglione wrote:
> On Fri, Mar 10, 2017 at 01:55:40PM +, David Burns wrote:
> >I went back and did some checks with autoland to servo and the results are
> >negligible. So from 01 February 2017 to 10 March 2017 (as of sending this
> >email). I
On Fri, Mar 10, 2017 at 01:55:40PM +, David Burns wrote:
I went back and did some checks with autoland to servo and the results are
negligible. So from 01 February 2017 to 10 March 2017 (as of sending this
email). I have removed merge commits from the numbers.
Autoland:
Total Servo Sync Push
I seem to recall gps saying, a few years ago, that the cost per push or
Try run was about $36. It would be good to know the current cost so
developers can feel more comfortable spending Mozilla money on
"unnecessary" Try runs before landing.
On 3/10/2017 6:47 AM, Andrew Halberstadt wrote:
I
I don't have any data to back this up, but my suspicion is that a large
percentage
of backouts had try runs, but said try runs didn't run the jobs that failed
and caused
the backout. Imo, these kinds of backouts are (more) acceptable because it
means
the developer was trying to avoid doing a full t
I went back and did some checks with autoland to servo and the results are
negligible. So from 01 February 2017 to 10 March 2017 (as of sending this
email). I have removed merge commits from the numbers.
Autoland:
Total Servo Sync Pushes: 152
Total Pushes: 1823
Total Backouts: 144
Percentage of ba
I don't know that it's useful to modify your report if you're confident in
your estimates below. Thanks for the additional information.
Lawrence
On Tue, Mar 7, 2017 at 4:03 AM, Carsten Book wrote:
> Hi Lawrence,
>
> most (i would say 95 %) of the backouts are for Code issues - this include
> bu
On 3/7/2017 3:38 AM, Joel Maher wrote:
One large difference I see between autoland and mozilla-inbound is that on
autoland we have many single commits/push whereas mozilla-inbound it is
fewer. I see the Futurama data showing pushes and the sheriff report
showing total commits.
autoland also in
latform-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
>&g
This is just a rough number of how many pushes had a backout and how many
didn't. I don't have any data on whether this is a full or partial backout.
If there are multiple bugs in a push on inbound, a sheriff may revert the
entire push (or might not depending on how obvious the error is and
availa
On 3/7/17 6:23 AM, David Burns wrote:
- Autoland 6%.(24 backouts out of 381 pushes)
- Inbound 12% (30 backouts out of 251 pushes)
Were those full backouts or partial backouts?
That is, how are we counting a multi-bug push to inbound where one of
the bugs gets backed out? Note that such
ht 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
> Datum: 2017-03-07 12:23
>
>> One thing that we hav
One large difference I see between autoland and mozilla-inbound is that on
autoland we have many single commits/push whereas mozilla-inbound it is
fewer. I see the Futurama data showing pushes and the sheriff report
showing total commits. Possibly there are some more data mining
opportunities :)
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 t
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 ne
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 wrote:
> Hi,
>
> We will be more active in 2017 and inform more about whats happening in
> Sheriffing and since its already M
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 w
17 matches
Mail list logo
