Re: [Sheriffs] Closure of trunk trees - owners for bugs needed

2013-10-31 Thread Carsten Book
Hi,

good morning.

Since the Trees are still closed here is a update as of 0:45am Pacific Time

* https://bugzilla.mozilla.org/show_bug.cgi?id=932898 has an owner now 
* https://bugzilla.mozilla.org/show_bug.cgi?id=932880 Patch landed on inbound 
and tests are running.

Cheers,

- Tomcat


- Original Message -
From: Ed Morley emor...@mozilla.com
To: Sheriffs sheri...@mozilla.org, dev.tree-management 
dev-tree-managem...@lists.mozilla.org, dev.platform 
dev-platform@lists.mozilla.org
Sent: Wednesday, October 30, 2013 7:04:45 PM
Subject: [Sheriffs] Closure of trunk trees - owners for bugs needed

Hi all!

Trunk trees are currently closed [1] - the requirements for reopening are:
https://bugzilla.mozilla.org/show_bug.cgi?id=932781#c11

tl;dr we need owners for these bugs:
* https://bugzilla.mozilla.org/show_bug.cgi?id=932898
* https://bugzilla.mozilla.org/show_bug.cgi?id=932880

Please can anyone who has any spare cycles take a look! :-)

Best wishes,

Ed

[1] Apart from b2g-inbound, since that doesn't run Windows 7 tests, 
which are the ones that are being the most problematic.

On 30 October 2013 14:09:47, Ed Morley wrote:
 I've broken the tree closing issues out into
 https://bugzilla.mozilla.org/show_bug.cgi?id=932781 and pasted the
 relevant parts of the IRC conversations from last night, because the
 OOMs are not constrained to that one existing bug  it's good to get
 the IRC chat saved somewhere visible (I've only just managed to piece
 together what has been tried so far and where we're at).

 khuey is kindly looking at this some more once he's gotten sorted :-)

 Ed
___
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


Fwd: Please take part in the Sheriff Survey

2015-03-23 Thread Carsten Book
Hey Guys,

thanks for all the Community Members who already did part in the Sheriff
Survey!

And just as reminder that the Survey is still up and running this week here
-http://goo.gl/forms/kRXZDtSjSj

Thanks!

- Tomcat


-- Forwarded message --
From: Carsten Book cb...@mozilla.com
Date: Mon, Mar 16, 2015 at 3:39 PM
Subject: Please take part in the Sheriff Survey
To: dev-platform@lists.mozilla.org


Hi,

When we moved to the inbound model of tree management, the Tree Sheriffs
became a crucial part of our engineering infrastructure. The primary
responsibility of the Sheriffs is and will always be to aid developers to
easily, quickly, and seamlessly land their code in the proper location(s)
and ensure that code does not break our automated tests. In the service of
this objective, the Sheriffs work closely with the larger engineering
organization to create and enforce landing policies that increase
productivity while maintaining an efficient and robust automated testing
system. Beyond the policy role, they have also become shepherds of
automation quality by monitoring intermittent failures, performing uplifts
and merges, and identifying poorly performing automation machines. This
role has proven successful, and so a formal module for the Tree Sheriffs in
the larger context of the Activities Module was created.

But of course there is always room for improvements and ideas how we can
make things better. In order to get a picture from our Community how things
went and how we can improve our day-to day-work.

So we created the Sheriff Survey here - http://goo.gl/forms/kRXZDtSjSj

Thanks for taking part in that!

- The Mozilla Tree Sheriffs!
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriffing Newsletter October Edition

2015-10-30 Thread Carsten Book
Hi,

To give a little insight into our work and make our work more visible to
our Community we decided to create a monthly report of what's going on in
the Sheriffs Team.

If you have questions or feedback, just let us know!

In case you don't know who the sheriffs are, or to check if there are
current issues on the tree, see:
https://sheriffs.etherpad.mozilla.org/sheriffing-notes

Topics of this month!

1. How-To article of the month
2. Get involved
3. Statistics
4. Orange Factor
5. Meeting notes
6. Contact

1. How-To article of the month and notable things!

Ever had a question about checking patches in, getting them backed out, or
any other related topic? The Sheriff Team is here to help! We usually hang
out in #developers on Mozilla's IRC network, and you can find the current
sheriff on duty by looking for the "|sheriffduty" tag on the name. We try
to rotate in order to cover every time zone. You can also reach us by email
via sheriffs at mozilla dot com.

2. Get involved!

Are you interested in helping out by becoming a Community Sheriff? Let us
know!

3. Statistics

Intermittent Bugs filed this month [1]: 312

and 17 Bugs of this Closed this Month [2]

For Tree Closing times and reasons see:
http://futurama.theautomatedtester.co.uk/

4. Orange Factor

Current Orangefactor [3]: 13.83

5. Meeting Notes:

We Sheriffs hold regular meetings. Our notes can be found here:

https://public.etherpad-mozilla.org/p/Sheriff-meeting-26oct

6.  How to contact us

There are a lot of ways to contact us. The fastest one is to contact
the sheriff on duty (the one with the |sheriffduty tag on their nick
:) or by emailing sheriffs @ mozilla dot org.

Cheers,

Tomcat

[1] http://mzl.la/1P9eZl8
[2] http://mzl.la/1XDtaBZ
[3] https://brasstacks.mozilla.com/orangefactor/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Questions about how to land stuff etc ?

2015-10-20 Thread Carsten Book
Hi,

we as Sheriffs get sometimes questions what to take care of when you want
to set the checkin-needed keyword and how the process goes etc ? Or what do
if you want/need to do a security bug checkin?

So when you anytime any question about checkins and stuff let us know. The
Sheriff Team is there for you to help and you can reach us anytime in irc -
you find the sheriff on duty with the |sheriffduty tag on the name - or via
email sheriffs at mozilla dot com.

cheers,

- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriffing Newsletter September!

2015-09-01 Thread Carsten Book
Hi,

to give a little insight into our work and make our work more visible
 for our Community we decided to create a new monthly report from
whats going on in the Sheriffs Team and our work.

If you have questions or feedback just let us know!

This is the first edition of this newsletter so let me know what you think
of it.

In case you don't know who are the sheriffs and if there are current
 issues on the tree see:

https://sheriffs.etherpad.mozilla.org/sheriffing-notes

Topics of this months!
1. Ryan's last week as sheriff!
2. How-To article of the month
3. Get involved
4. Statistics
5. Orange Factor
6. Meeting notes
7. Contact

1. Ryan's last week as Sheriff!

As you might have heard that RyanVM is leaving the Sheriff Team to he will
be leading a new quality team as part of the Firefox org. So its his last
week as Sheriff this week.
Thanks for all what do you did for keeping the Trees open and making the
Sheriff-Role and Sheriffing what it is today and all the best for your new
Role Ryan!

Also of course there will be other Sheriffs around if you have questions
let us know anytime (see the contact section below).

2. How-To Article of the month :) - Notable things!

Ever wondered how Sheriffs do work ? We have a lot of how-to articles
 here: https://wiki.mozilla.org/Sheriffing/How:To

We also do checkins for checkin-needed requests. We have documented
this task here
https://wiki.mozilla.org/Sheriffing/How:To:Landing_checkin-needed_patches
and we are always interested in feedback and how we can make things
better.

3. Get involved!

Ever interested in getting a Community Sheriff and helping checking
test results ? Let us know !

4. Statistics

Intermittent Bugs filed last month [1] : 309
Intermittent Bugs closed last month [2] : 190

For Tree Closing times and reasons see :
http://futurama.theautomatedtester.co.uk/

5. Orange Factor

Current Orangefactor [3] : 7.89

6. Meeting Notes:*

We Sheriffs hold regular meetings. Our notes can be found here:

https://sheriffs.etherpad.mozilla.org/meeting-2015-08-03
and
https://sheriffs.etherpad.mozilla.org/meeting-2015-08-31

7.  How to contact us ?

There are a lot of ways to contact us. The fastest one is to contact
the sheriff on duty (the one with the |sheriffduty tag on this nick
:) or by emailing sheriffs @ mozilla dot org

Cheers,

on behalf of the Sheriff Team
- Tomcat

[1]: http://mzl.la/1KQsqmZ
 [2]: http://mzl.la/1SNM4Hg
 [3]:https://brasstacks.mozilla.com/orangefactor/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriffing Newsletter, End of September Edition

2015-09-28 Thread Carsten Book
Hi,

To give a little insight into our work and make our work more visible to
our Community we decided to create a  monthly report of what's going on in
the Sheriffs Team.

If you have questions or feedback just let us know!

In case you don't know who the sheriffs are or if there are current issues
on the tree, see:
https://sheriffs.etherpad.mozilla.org/sheriffing-notes

Topics of this month!

1. How-To article of the month
2. Get involved
3. Statistics
4. Orange Factor
5. Meeting notes
6. Contact

1. How-To article of the month and notable things!

First: Welcome Nigel Babu (irc: nigelb) our latest addition to the Sheriffs
Team!

Also a  few words about checkin-needed requests since we got some questions
during the month.

-> Work is being done on an autolander system that lands your patches to
mozilla-inbound for example. However that system is not ready yet, so all
checkin-needed requests are being handled by a human and not automated.

->  When you have multiple check-ins that need to land, it would be helpful
if you could indicate in the checkin-needed request which dependencies the
bug has, or which parts of the patches you want to get landed (like part 3
to 4 etc)

-> It would be super helpful if your commit message on the patch you want
to get checked-in is complete with bug number, title and reviewer name.
This helps a lot!

2. Get involved!

Are you interested in becoming a Community Sheriff and helping oversee
test results? Let us know!

3. Statistics

Intermittent Bugs filed this month [1]: 400
Intermittent Bugs closed this month [2]: 214

For Tree Closing times and reasons see:
http://futurama.theautomatedtester.co.uk/

4. Orange Factor

Current Orangefactor [3]: 8.77

5. Meeting Notes:

We Sheriffs hold regular meetings. Our notes can be found here:

https://sheriffs.etherpad.mozilla.org/meeting-2015-09-14
https://sheriffs.etherpad.mozilla.org/meeting-2015-09-21

6.  How to contact us

There are a lot of ways to contact us. The fastest one is to contact
the sheriff on duty (the one with the |sheriffduty tag on their nick
:) or by emailing sheriffs @ mozilla dot org.

Cheers,

[1]: http://mzl.la/1LgxbKc
[2]: http://mzl.la/1PJ287C
[3]: https://brasstacks.mozilla.com/orangefactor/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Help needed for Bugs keeping the Aurora Tree Closed after the 44->45 Uplift

2015-12-16 Thread Carsten Book
Hi,

we currently have the Aurora Tree closed since we have some test failures
etc after the merge from 44-45 on Monday.

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1233066 as tracking
bug for this issues and it would be greatly appreciated if we could fix
this asap to reopen aurora for uplifts.

So any help welcome here, the bugs are listed as dependency from bug
1233066 that keep the keep the trees closed.

Cheers,

- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Thanks for all the great teamwork with the Sheriffs in 2015!

2015-12-30 Thread Carsten Book
Hi,

Sheriffing is not just about Checkins, Uplifts and Backouts - its also a
lot of teamwork with different Groups and our Community like Developers, IT
Teams and Release Engineering and a lot more to keep the trees up and
running. And without this great teamwork our job would be nearly impossible!

So far in 2015 we had around:

56471 changesets with 336218 changes to 70807 files in mozilla-central
and 4391 Bugs filed for intermittent failures (and a lot of them fixed).

So thanks a lot for the great teamwork with YOU in 2015 - especially also a
great thanks to our Community Sheriffs like philor, nigelb and Aryx who
done great work!

I hope we can continue this great teamwork in 2016 and also the monthly
sheriff report with interesting news from the sheriffs and how you can
contribute will continue then :)

Have a great start into 2016!

Tomcat
on behalf of the Sheriffs-Team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


[no subject]

2015-12-01 Thread Carsten Book
Hi,

To give a little insight into our work and make our work more visible to
our Community we decided to create a  monthly report of what's going on in
the Sheriffs Team.

If you have questions or feedback, just let us know!

In case you don't know who the sheriffs are, or to check if there are
current issues on the tree, see:
https://sheriffs.etherpad.mozilla.org/sheriffing-notes

Topics of this month!

1. How-To article of the month
2. Get involved
3. Statistics
4. Orange Factor
5. Meeting notes
6. Contact

1. How-To article of the month and notable things!

Sheriffs also do uplifts (like to mozilla-aurora, mozilla-beta, etc) - The
how-to page we use for that is mainly:
https://wiki.mozilla.org/Sheriffing/How:To:Uplifts


2. Get involved!

Are you interested in helping out by becoming a Community Sheriff? Let us
know!

3. Statistics

Intermittent Bugs filed this month [1]: 319
and 19 of them are closed [2]

For Tree Closing times and reasons see:
http://futurama.theautomatedtester.co.uk/

4. Orange Factor

Current Orangefactor [3]: 16:36

5. Meeting Notes:

We Sheriffs hold regular meetings. Our notes can be found here:

https://public.etherpad-mozilla.org/p/Sheriff-meeting-16nov

6.  How to contact us

There are a lot of ways to contact us. The fastest one is to contact
the sheriff on duty (the one with the |sheriffduty tag on their nick
:) or by emailing sheriffs @ mozilla dot org.

Cheers,

- Tomcat

[1] http://mzl.la/1PrCHei
[2] http://mzl.la/1QRza9e
[3] https://brasstacks.mozilla.com/orangefactor/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriff Coverage during Mozilla London All-hands next week

2016-06-07 Thread Carsten Book
Hi,

as you know London All-Hands is coming up soon. This affects also sheriff
coverage of trees since Kwierso and me (Tomcat) will be also attending the
all-hands in London.

While we try to check the Trees every now and then and have Community
Sheriffs around we can not guarantee the normal tree coverage as usual
(that also include checkin-needed tasks).

In case of urgent issues/tasks please needinfo :Kwierso and/or me :Tomcat
in bugzilla or email us directly.

If you are in London and want to talk with us about everything Sheriff
Related, feel free to poke us anytime!

Cheers,
on behalf of the Sheriffs,

- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Mozilla Sheriff Survey

2016-06-08 Thread Carsten Book
Hi,

When we moved to the "inbound" model of tree management, the Tree Sheriffs
became a crucial part of our engineering infrastructure. The primary
responsibility of the Sheriffs is and will always be to aid developers to
easily, quickly, and seamlessly land their code in the proper location(s)
and ensure that code does not break our automated tests.

But of course there is always room for improvements and ideas how we can
make things better. In order to get a picture from our Community (YOU!) how
things went and how we can improve our day-to day-work we created a Survey!
You can find the Survey here:

http://bit.ly/1tgHtCR

Thanks for taking part in this survey!

Also you can find some of us also in London during the Mozilla All-hands if
you want to talk to us directly!

Cheers,

- Tomcat
on behalf of the Sheriffs Team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


mozlondon - meet the sheriffs

2016-06-14 Thread Carsten Book
Hi,

Sheriffs are also in London and if you would like to talk anything sheriff
related or so, just ping kwierso or me in irc or drop me a mail and we can
get in touch with you.

Looking forward to meet you in Person!

om behalf of the sheriffs
- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriff Newsletter for January 2016

2016-02-02 Thread Carsten Book
Hi,

To give a little insight into our work and make our work more visible to
our Community we decided to create a  monthly report of what's going on in
the Sheriffs Team.

If you have questions or feedback, just let us know!

In case you don't know who the sheriffs are, or to check if there are
current issues on the tree, see:
https://public.etherpad-mozilla.org/p/sheriffing-notes

Topics of this month!

1. How-To article of the month
2. Get involved
3. Statistics for January
4. Orange Factor
5. Contact

1. How-To article of the month and notable things!

-> In the Sheriff Newsletter we mentioned the "Orange Factor" but what is
this ?  It is simply the ratio of oranges (test failures) to test runs. The
ideal value is, of course, zero.

Practically, this is virtually impossible for a code base of any
substantial size,so it is a matter of policy as to what is an acceptable
orange factor.

It is worth noting that the overall orange factor indicates nothing about
the severity of the oranges. [4]

The main site where you can checkout the "Orange Factor" is at
https://brasstacks.mozilla.com/orangefactor/  and some interesting info's
are here https://wiki.mozilla.org/Auto-tools/Projects/OrangeFactor

-> As you might be aware Firefox OS has moved into Tier 3 Support [5] -
this means that there is no Sheriff Support anymore for the b2g-inbound
tree.

Also with moving into tier-3 - b2g tests have also moved to tier 3 and this
tests are by default "hidden" on treeherder. To view test results as
example on treeherder for mozilla-central you need to click on the checkbox
in the treeview "show/hide excluded jobs".

2. Get involved!

Are you interested in helping out by becoming a Community Sheriff? Let us
know!

3. Statistics

Intermittent Bugs filed in January  [1]: 667
and of those are closed: 107 [2]

For Tree Closing times and reasons see:
http://futurama.theautomatedtester.co.uk/

4. Orange Factor

Current Orangefactor [3]: 12.92

5.  How to contact us

There are a lot of ways to contact us. The fastest one is to contact
the sheriff on duty (the one with the |sheriffduty tag on their nick
:) or by emailing sheriffs @ mozilla dot org.

Cheers,

- Tomcat on the behalf of the Sheriffs

[1] http://mzl.la/1NOD4Zz
[2] http://mzl.la/1mas9TS
[3]
https://brasstacks.mozilla.com/orangefactor/?display=OrangeFactor=2016-02-01=2016-01-01=trunk
[4]
http://people.mozilla.org/~mcote/war-on-orange/war-on-orange-paper-testistanbul.pdf
[5]
https://groups.google.com/d/msg/mozilla.dev.platform/gF-kiJV21ro/qJRk1B-KAAAJ
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Tree Closures due to Bug 1286942 Buildbot DB Issues

2016-07-15 Thread Carsten Book
Hi,

we currently have a complete tree closure due to Buildbot DB Issues.

The Teams working on resolving this issue and the Tracking Bug is:
https://bugzilla.mozilla.org/show_bug.cgi?id=1286942

There is no ETA yet for reopening.

Thanks for your patience.

- Tomcat

P.S. one way to get patches checked-in automatically would be using
MozReview and Autoland to push it when then tree reopens.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: [Sheriffs] Current state of the tree closures

2016-07-19 Thread Carsten Book
Hi,

thanks Wes!

taking over now and cleaning up the trees the sheriffed repos and will do
backouts as needed.

- Tomcat

On Tue, Jul 19, 2016 at 4:05 AM, Wes Kocher  wrote:

> The Treeherder devs have deployed a hotfix that appears to have fixed up
> the responsiveness issues, so I've reopened the trees.
>
> On Mon, Jul 18, 2016 at 5:05 PM, Wes Kocher  wrote:
>
>>
>> The DB issues that popped back up again from bug 1286942 have been
>> resolved, and all non-trunk trees have been reopened.
>>
>> Treeherder responsiveness has been an issue all day (bug 1287501), which
>> is keeping the trunk trees closed, since I can't easily tell if jobs are
>> broken. The responsiveness issues are still ongoing as of 5pm Pacific, so
>> I'm leaving the trees closed.
>>
>> As with last week's closure, queuing up your pushes in autoland would be
>> the easiest way to ensure your patches land when trees reopen.
>>
>
>
> ___
> 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


Re: Autoland to mozilla-central updates currently blocked

2016-07-04 Thread Carsten Book
Hi,

all resolved now and will update now autoland to m-c on a regular base!

Thanks to gps for resolving the problem!

Cheers,
- tomcat

On Mon, Jul 4, 2016 at 10:08 AM, Carsten Book <cb...@mozilla.com> wrote:

> Hi,
>
> just in case someone wonders (and since i got pinged by a couple of
> people).
>
> Currently due to https://bugzilla.mozilla.org/show_bug.cgi?id=1283798#c5
> we cannot update/merge/rebase autoland to mozilla-central currently.
>
> We are working on this and gps is aware of this - but due to the US
> holiday today it might could take some time today to get that fixed.
>
> Thanks for you patience and sorry for the inconvenience.
>
> - Tomcat
>
>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Mozilla Sheriff Survey is still open for your input!

2016-07-05 Thread Carsten Book
Hi,

a little reminder that the survey is still online for another week. So this
is your chance to give us feedback and tell us your ideas! Every Feedback
helps ! :)

Cheers,
- Tomcat

On Wed, Jun 8, 2016 at 12:54 PM, Carsten Book <cb...@mozilla.com> wrote:

> Hi,
>
> When we moved to the "inbound" model of tree management, the Tree Sheriffs
> became a crucial part of our engineering infrastructure. The primary
> responsibility of the Sheriffs is and will always be to aid developers to
> easily, quickly, and seamlessly land their code in the proper location(s)
> and ensure that code does not break our automated tests.
>
> But of course there is always room for improvements and ideas how we can
> make things better. In order to get a picture from our Community (YOU!) how
> things went and how we can improve our day-to day-work we created a Survey!
> You can find the Survey here:
>
> http://bit.ly/1tgHtCR
>
> Thanks for taking part in this survey!
>
> Also you can find some of us also in London during the Mozilla All-hands
> if you want to talk to us directly!
>
> Cheers,
>
> - Tomcat
> on behalf of the Sheriffs Team
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Checkin-needed requests - Please include complete information in the commit message :)

2016-07-08 Thread Carsten Book
Hi,

someone might not know that doing checkins for checkin-needed request is
not automated yet and completely a fully human task :) (no we Sheriffs are
not bots ;)

It would help us a lot if a checkin needed request would contain complete
Author/Patch information like:


   - Author (use the information from their Bugzilla account if needed)
   with Name *and *Emailadress.
   - Bug number
   - Commit message (keeping in mind that the commit message should be a
   brief description of what the patch is *doing*)
  - Format should be something like "Bug 123456 - Add a null check to
  XYZ to avoid a crash. r=somebody"


And also if there is a specific sequence/dependency you want to checkin the
patches it would help also a lot  if you could make a short comment in the
Bug like please checkin part x then patch y or like first bug 123 then this
bug and then bug 8910.

This would help us a lot :)

Thanks!

- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriff Highlights and Summary in January 2017

2017-02-01 Thread Carsten Book
Hi,

We will be more active in 2017 and we blog more about whats happening in
Sheriffing.

So happened in January in 2017 in Sheriffing.

Sheriffs monitored in January 2017 about  ~ 4121 checkins (including merge
changesets) to mozilla-central with commits coming from the integration
branches.

In this ~ 4121 checkins are about ~ 302 Backouts for various reasons.

Beside this, Sheriffs took part in doing checkin-needed landings, uplifts
and making sure Trees are ok after merge day when Trunk moved to
Mozilla/Firefox-54.

The Current Orangefactor is 12.6 (7818 test failures failures in 620 pushes
in the last 7 days).

You can find the list of top Intermittent failure bugs here
https://brasstacks.mozilla.com/orangefactor/

You can find more general statistics here: http
s

://futurama.theautomatedtester.co.uk/


Initiatives Sheriffs currently involved or Meetings happened this month:

-> we are working with James Graham to improve Auto-Classfication
-> looking into how we can support
https://wiki.mozilla.org/Auto-tools/Projects/Stockwell/Meetings with making
sure bugs are addressed.

Also as part of more blogging about Sheriffing we published a post about
checkin-neededs bug
https://blog.mozilla.org/tomcat/2017/01/26/sheriffing-mozilla-checkin-needed/

Let us know when you have any Question or Feedback about Sheriffing.

On behalf of the Sheriffs,

- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriff Highlights and Summary in March 2017 (and even Q1 2017)

2017-04-04 Thread Carsten Book
Hi,

We will be more active in 2017 and inform more about whats happening in
Sheriffing and since its already April..lets go :)

The Paid Sheriffs (kwierso and me) are now reporting to Chris Cooper (coop)
and we would like to thank David Burns (Automatedtester) for his
awesomeness in leading and guiding us the last years and we are excited to
rock Sheriffing with Coop!

A lot of Interest in the last weekswas about the Tree Statistics ,so with
the help of a Script from Automatedtester here are some more detailed
information about our work on the integration trees:

*March 2017:*

*Autoland Tree:*
Total Servo Sync Pushes: 219
Total Pushes: 1655
Total Number of commits 3851
Total number of commits without Servo 3627
Total Backouts: 137
Total of Multi-bug pushes 20 (note this are in the autoland case, sheriffs
tree merges from mozilla-central to autoland)
Total number of bugs changed 1564
Percentage of backout against bugs: 8.75959079284
Percentage of backouts: 8.27794561934
Percentage of backouts without Servo: 9.54038997214

*Mozilla-Inbound*
Total Pushes: 1071
Total Number of commits 3471
Total Backouts: 138
Total of Multi-bug pushes 189
Total number of bugs changed 1478
Percentage of backout against bugs: 9.33694181326
Percentage of backouts: 12.8851540616

*For Q1* (since end of March was also Q1/2017 end) the overall data look
like:

*Autoland Q1:*

Total Servo Sync Pushes: 317
Total Pushes: 4099
Total Number of commits 9710
Total number of commits without Servo 9349
Total Backouts: 362
Total of Multi-bug pushes 56 (Sheriff managed integration tree merges from
mozilla-central to autoland)
Total number of bugs changed 4348
Percentage of backout against bugs: 8.32566697332
Percentage of backouts: 8.83142229812
Percentage of backouts without Servo: 9.57165520888


*Mozilla-Inbound Q1*

Total Pushes: 3271
Total Number of commits 18209
Total Backouts: 378
Total of Multi-bug pushes 571
Total number of bugs changed 4630
Percentage of backout against bugs: 8.16414686825
Percentage of backouts: 11.5560990523


So Sheriffs managed and monitored on the Integration Trees in March 2017 ~
2700 pushes and 275 backouts.

Overall in Q1 2017 we managed and monitored 7370 pushes and 740 backouts on
the Integration Trees.

Also blogged about Backouts & Sheriffing in
https://blog.mozilla.org/tomcat/2017/04/03/sheriffing-and-backouts/

Beside this Sheriffs took park in doing uplifts and checkin-needed bugs.

The Current Orangefactor is 10.11 (7392 test failures failures in 731
pushes in the last 7 days). You can find the list of top Intermittent
failure bugs here https://brasstacks.mozilla.com/orangefactor/

You can find more statistics here:
https://futurama.theautomatedtester.co.uk/

If you want also to be a Community Sheriffs, as part of more blogging
about Sheriffing i published a blog post about it and let us know if you
want to be involved! :
https://blog.mozilla.org/tomcat/2017/02/27/community-sheriffs/

Let us know when you have any Question or Feedback about Sheriffing.

Cheers and have a great April!,
-Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Sheriff Highlights and Summary in February 2017

2017-03-07 Thread Carsten Book
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>
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> 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/
>>
>> You can find more statistics here: https://futurama.theautomatedt
>> ester.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-sheriffs/
>>
>> Let us know when you have any Question or Feedback about Sheriffing.
>>
>> Cheers,
>>  -Tomcat
>>
>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: [Sheriffs] Sheriff Highlights and Summary in February 2017

2017-03-07 Thread Carsten Book
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.theautomated
>> tester.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 > 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/>

Sheriff Highlights and Summary in February 2017

2017-03-01 Thread Carsten Book
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/

You can find more statistics here:
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-sheriffs/

Let us know when you have any Question or Feedback about Sheriffing.

Cheers,
 -Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriff Statistics for June 2017

2017-07-03 Thread Carsten Book
Hi,

Welcome to the Sheriff Statistics for June 2017 !

Also i would like to thank everyone for taking part in the Sheriff Survey -
You can see the results here :
https://blog.mozilla.org/tomcat/2017/06/23/sheriff-survey-results/

Now to the actual data for June!

*June 2017:*

*Autoland Tree:*

Total Servo Sync Pushes: 254
Total Pushes: 1799
Total Number of commits 3711
Total number of commits without Servo 3445
Total Backouts: 167
Total of Multi-bug pushes 12
Total number of bugs changed 1702
Percentage of backout against bugs: 9.81198589894
Percentage of backouts: 9.28293496387
Percentage of backouts without Servo: 10.8090614887 (thats ~ +0,8 % higher
rate compared to may)

*Mozilla-inbound*

Total Servo Sync Pushes: 0
Total Pushes: 1117
Total Number of commits 3611
Total number of commits without Servo 3611
Total Backouts: 130
Total of Multi-bug pushes 159
Total number of bugs changed 1591
Percentage of backout against bugs: 8.17096165933
Percentage of backouts: 11.6383169203
Percentage of backouts without Servo: 11.6383169203 (~ +0,7 % higher rate
compared to may)


So Sheriffs managed and monitored on the Integration Trees in May 2017 ~
2900 pushes and 297 backouts.

Let us know when you have any Question or Feedback about Sheriffing.

Cheers and have a great July!,
-Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Reminder: Please Take Part in the Sheriff Survey

2017-06-19 Thread Carsten Book
Hi,
just a reminder that we have our Sheriff Survey Running and please take
part in it, it helps us a lot to improve our work!

Link:
https://docs.google.com/a/mozilla.com/forms/d/e/1FAIpQLSfGBZ50zkG9W-Wnk1ACBfFvj1iu8e46I5gs9t-G3ZWDpcy4-A/viewform

thanks!

- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriff Survey Results

2017-06-23 Thread Carsten Book
Hi,

first a super big thanks for taking part in this years Sheriff Survey -
this helps us a lot !

Here are the results.

1. Overall "satisfaction" - we have asked how People rate their interaction
with us (from 1 (bad) to 10 (best)

So far from all results:

3,1 % = 5
3,1 % = 7
12,5 % = 8
43,8 % = 9
37,5 % = 10

2. What can we do better  as Sheriffs?

We got a lot of Feedback thats its not easy to find out who is on
"sheriffduty". We will take steps (like adding |sheriffduty tag to irc
names etc) also we have https://bugzilla.mozilla.org/show_bug.cgi?id=1144589
with the target to have that name on treeherder.

Also we try to make sure to Set Needinfo requests on Backouts.

In any case, backouts are never meant to be personal and it’s part of our
job to try our best to keep our trees open for developers. We also try to
provide as much information as possible in the bug for why we
backed out a change.

3. Things we can improve in general (not just sheriffs) ?

A interesting Idea in the Feedback we got was about Automation. We will
follow up from the Feedback and i already filed
https://bugzilla.mozilla.org/show_bug.cgi?id=1375520 for the Idea of having
a "Backout Button" in Treeherder in case no Sheriff is around etc - more
bugs from ideas to improve general stuff and workflows will follow.

Again thanks for taking part in the Survey and if you have
questions/feedback/concerns/ideas you can of course contact me / the team
at anytime !

Cheers,

- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriff Survey started & Sheriff Statistics May 2017

2017-06-07 Thread Carsten Book
Hi,

just one second before i start into statistics

One thing i love at Mozilla is that there is no general "that's the way we
have always done it.." - we at Mozilla also try to improve things - our
Software but also our processes and so its also with Sheriffing - We try to
optimize our workflow/processes constantly to make your live as developer
easier when working with us but ... we rely also on your feedback :)

So we created a Survey for YOU to give us Feedback about how we do and also
where we can improve. This input/Feedback from you is very valuable for us!

You can find the Survey at http://bit.ly/2rzMjNi -
https://docs.google.com/a/mozilla.com/forms/d/1a8QmBraKjW750WVU01pbsWwE-KU2j10dHHWJx5cGi0g

Thanks for taking part in the Survey!

and now the Statistics for May 2017

*May 2017:*

*Autoland Tree:*

Total Servo Sync Pushes: 266
Total Pushes: 1848
Total Number of commits 3959
Total number of commits without Servo 3664
Total Backouts: 157
Total of Multi-bug pushes 14
Total number of bugs changed 1714
Percentage of backout against bugs: 9.15985997666
Percentage of backouts: 8.49567099567
Percentage of backouts without Servo: 9.92414664981 (also more commits in
May compared April and backout rate drop of  -0,6 %)

*Mozilla-inbound*

Total Servo Sync Pushes: 0
Total Pushes: 1059
Total Number of commits 3823
Total number of commits without Servo 3823
Total Backouts: 116
Total of Multi-bug pushes 178
Total number of bugs changed 1433
Percentage of backout against bugs: 8.09490579204
Percentage of backouts: 10.9537299339
Percentage of backouts without Servo: 10.9537299339 (more pushes in May
compared to April and -3 % drop of the backout rate!


So Sheriffs managed and monitored on the Integration Trees in May 2017 ~
2900 pushes and 335 backouts.

Let us know when you have any Question or Feedback about Sheriffing.

Cheers and have a great June!,
-Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Sheriff Survey started & Sheriff Statistics May 2017

2017-06-07 Thread Carsten Book
since some people had problems filing out the survey - some better links :)

http://bit.ly/2s4rACF -
https://docs.google.com/a/mozilla.com/forms/d/e/1FAIpQLSfGBZ50zkG9W-Wnk1ACBfFvj1iu8e46I5gs9t-G3ZWDpcy4-A/viewform

<https://docs.google.com/a/mozilla.com/forms/d/e/1FAIpQLSfGBZ50zkG9W-Wnk1ACBfFvj1iu8e46I5gs9t-G3ZWDpcy4-A/viewform>
sorry
- Tomcat

<https://docs.google.com/a/mozilla.com/forms/d/e/1FAIpQLSfGBZ50zkG9W-Wnk1ACBfFvj1iu8e46I5gs9t-G3ZWDpcy4-A/viewform>

On Wed, Jun 7, 2017 at 10:58 AM, Carsten Book <cb...@mozilla.com> wrote:

> Hi,
>
> just one second before i start into statistics
>
> One thing i love at Mozilla is that there is no general "that's the way we
> have always done it.." - we at Mozilla also try to improve things - our
> Software but also our processes and so its also with Sheriffing - We try to
> optimize our workflow/processes constantly to make your live as developer
> easier when working with us but ... we rely also on your feedback :)
>
> So we created a Survey for YOU to give us Feedback about how we do and
> also where we can improve. This input/Feedback from you is very valuable
> for us!
>
> You can find the Survey at http://bit.ly/2rzMjNi -
> https://docs.google.com/a/mozilla.com/forms/d/1a8QmBraKjW750WVU01pbsWwE-
> KU2j10dHHWJx5cGi0g
>
> Thanks for taking part in the Survey!
>
> and now the Statistics for May 2017
>
> *May 2017:*
>
> *Autoland Tree:*
>
> Total Servo Sync Pushes: 266
> Total Pushes: 1848
> Total Number of commits 3959
> Total number of commits without Servo 3664
> Total Backouts: 157
> Total of Multi-bug pushes 14
> Total number of bugs changed 1714
> Percentage of backout against bugs: 9.15985997666
> Percentage of backouts: 8.49567099567
> Percentage of backouts without Servo: 9.92414664981 (also more commits in
> May compared April and backout rate drop of  -0,6 %)
>
> *Mozilla-inbound*
>
> Total Servo Sync Pushes: 0
> Total Pushes: 1059
> Total Number of commits 3823
> Total number of commits without Servo 3823
> Total Backouts: 116
> Total of Multi-bug pushes 178
> Total number of bugs changed 1433
> Percentage of backout against bugs: 8.09490579204
> Percentage of backouts: 10.9537299339
> Percentage of backouts without Servo: 10.9537299339 (more pushes in May
> compared to April and -3 % drop of the backout rate!
>
>
> So Sheriffs managed and monitored on the Integration Trees in May 2017 ~
> 2900 pushes and 335 backouts.
>
> Let us know when you have any Question or Feedback about Sheriffing.
>
> Cheers and have a great June!,
> -Tomcat
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Proposal for informing Developers and Sheriffs about new Testsuites

2017-06-14 Thread Carsten Book
i guess sheriffs list (sheriffs @ m.o ) and newsgroup dev.platform, fx -dev
but i'm also open for suggetions from others :)

- tomcat

On Wed, Jun 14, 2017 at 4:12 PM, Kartikaya Gupta <kgu...@mozilla.com> wrote:

> This sounds good to me. What mailing lists should the intent email be
> sent to? It might help to have a template somewhere as well.
>
> On Wed, Jun 14, 2017 at 4:58 AM, Carsten Book <cb...@mozilla.com> wrote:
> > Hi,
> >
> > we had the case that a new testsuite was enabled and one test of that
> suite
> > resulted in a new perma orange failure. Its a tier-2 testsuite but of
> > course also tier 2 cause additional work for sheriffs.
> >
> > The Problem on new Testsuite is that Sheriffs are in a lot of cases not
> > informed about that new testsuite (so we need to find out who to contact
> > etc) and also it affects Developers because they might be confused why
> > their try run is showing a orange result they don't even know of (and
> waste
> > time in finding out if that test is red/orange because of their change).
> >
> > So i propose:
> >
> > People should email with an intent to implement when adding a new
> > platform/suite, and that email should contain links to docs/wiki/... and
> > the persons (in a super optimal case more than one just for timezone
> > coverage if sheriffs have question) we can contact in case of questions.
> >
> > this would benefit in :
> >
> > 1) sheriffs will know who to speak to if it's failing or needs to be
> hidden
> > - so we can assign bugs or even ping people directly on irc
> > 2) developers know what this new test is when they break it on their try
> > push and so save time and resources if the failure is known and sheriffs
> or
> > others can point to a bug/newsgroup mail
> > 3) discussions can be had about any overlap the new tests have with other
> > suites or say deciding what platforms it should run on etc
> >
> > I guess this would help Sheriffs and Developers. I initially was thinking
> > about about a changelog on treeherder for such changes but that have the
> > disadvantage that this would not include all the information we need to
> > contact someone etc
> >
> > I hope that this proposal make sense.
> >
> > Cheers,
> > - Tomcat
> > ___
> > dev-platform mailing list
> > dev-platform@lists.mozilla.org
> > https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Proposal for informing Developers and Sheriffs about new Testsuites

2017-06-14 Thread Carsten Book
Hi,

we had the case that a new testsuite was enabled and one test of that suite
resulted in a new perma orange failure. Its a tier-2 testsuite but of
course also tier 2 cause additional work for sheriffs.

The Problem on new Testsuite is that Sheriffs are in a lot of cases not
informed about that new testsuite (so we need to find out who to contact
etc) and also it affects Developers because they might be confused why
their try run is showing a orange result they don't even know of (and waste
time in finding out if that test is red/orange because of their change).

So i propose:

People should email with an intent to implement when adding a new
platform/suite, and that email should contain links to docs/wiki/... and
the persons (in a super optimal case more than one just for timezone
coverage if sheriffs have question) we can contact in case of questions.

this would benefit in :

1) sheriffs will know who to speak to if it's failing or needs to be hidden
- so we can assign bugs or even ping people directly on irc
2) developers know what this new test is when they break it on their try
push and so save time and resources if the failure is known and sheriffs or
others can point to a bug/newsgroup mail
3) discussions can be had about any overlap the new tests have with other
suites or say deciding what platforms it should run on etc

I guess this would help Sheriffs and Developers. I initially was thinking
about about a changelog on treeherder for such changes but that have the
disadvantage that this would not include all the information we need to
contact someone etc

I hope that this proposal make sense.

Cheers,
- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Sheriff Statistics for April 2017

2017-05-03 Thread Carsten Book
Hi,

We will be more active in 2017 and inform more and since its already
May..lets go :)

*April 2017:*

*Autoland Tree:*

Total Servo Sync Pushes: 251
Total Pushes: 1783
Total Number of commits 3544
Total number of commits without Servo 3281
Total Backouts: 161
Total of Multi-bug pushes 16 (merges from m-c to autoland)
Total number of bugs changed 1663
Percentage of backout against bugs: 9.68129885749
Percentage of backouts: 9.02972518228
Percentage of backouts without Servo: 10.5091383812 (compared to March
that's ~ +1 % higher - with a slightly higher rate of pushes)

*Mozilla-inbound*

Total Servo Sync Pushes: 0
Total Pushes: 1008
Total Number of commits 3374
Total number of commits without Servo 3374
Total Backouts: 134
Total of Multi-bug pushes 161
Total number of bugs changed 1294
Percentage of backout against bugs: 10.3554868624
Percentage of backouts: 13.2936507937
Percentage of backouts without Servo: 13.2936507937  (compared with March
that's ~ +0,5 % higher with around the same rate of commits)


So Sheriffs managed and monitored on the Integration Trees in April 2017 ~
2800 pushes and 295 backouts.

Beside this Sheriffs took park in doing uplifts and checkin-needed bugs.

The Current Orangefactor is 7.51 (5674 failures in 755 pushes in the last 7
days). You can find the list of top Intermittent
failure bugs here https://brasstacks.mozilla.com/orangefactor/

You can find more statistics here:
https://futurama.theautomatedtester.co.uk/

Let us know when you have any Question or Feedback about Sheriffing.

Cheers and have a great May!,
-Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Trees closed for OS X Test Job Backlog

2017-06-28 Thread Carsten Book
Hi,

currently integration trees are closed for
https://bugzilla.mozilla.org/show_bug.cgi?id=1376584 - a high job Backlog
on OS X.

We are working on it but unfortunately it's going to take quite a long time
to burn through that kind of backlog.

Sorry for the trouble.

- Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform