PSA: trybot removals (round #1)

[Paweł Hajdan, Jr.]

Hello Chrome developers,

to help make the Tryserver more maintainable, I'd like to remove unused and unmaintained trybots.

As part of this effort, I'd like to remove the following builders a week from now, on Nov 25:

tryserver.chromium.linux:

linux_chromeos_valgrind

linux_redux

linux_rel_naclmore

linux_valgrind

tryserver.chromium.mac:

mac_chromium_openssl_dbg

mac_chromium_openssl_rel

mac_rel_naclmore

mac_valgrind

mac_xcodebuild

tryserver.chromium.win:

win_rel_naclmore

Please help Chrome Infra make Tryserver an even friendlier, cleaner and more reliable piece of the build infrastructure. Don’t hesitate to respond with questions, concerns, or any other feedback.

Paweł

[Ryan Tseng]

SGTM.  I'm also wondering, for future reference:

1. Whats your criteria for removal?

2. We have a lot of builders, can we automate this on a dashboard?

--
You received this message because you are subscribed to the Google Groups "infra-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infra-dev+...@chromium.org.
To post to this group, send email to infr...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/infra-dev/CAATLsPbE2Lajgy63mQLVbsF6TVPOBu6hpXfpOQuVhkZ_maJ_BQ%40mail.gmail.com.

[Thiago Farina]

On Tue, Nov 18, 2014 at 4:13 PM, Ryan Tseng <hin...@chromium.org> wrote:

2. We have a lot of builders, can we automate this on a dashboard?

Hum, by "automate" here, what you mean? The removal? Sorry, I couldn't get it from the context.

 

--

Thiago Farina

[Ryan Tseng]

Sorry automate is a vague term.  I was thinking along the lines of "automatically generating a list of unused builders".

[Matt Mueller]

On Tue, Nov 18, 2014 at 3:01 AM, Paweł Hajdan, Jr. <phajd...@chromium.org> wrote:

Hello Chrome developers,

to help make the Tryserver more maintainable, I'd like to remove unused and unmaintained trybots.

As part of this effort, I'd like to remove the following builders a week from now, on Nov 25:

tryserver.chromium.linux:

linux_chromeos_valgrind

linux_redux

Any update on crbug.com/359533 ?

 

linux_rel_naclmore

linux_valgrind

Are we getting rid of the official valgrind bots too?

 

tryserver.chromium.mac:

mac_chromium_openssl_dbg

mac_chromium_openssl_rel

mac_rel_naclmore

mac_valgrind

mac_xcodebuild

tryserver.chromium.win:

win_rel_naclmore

Please help Chrome Infra make Tryserver an even friendlier, cleaner and more reliable piece of the build infrastructure. Don’t hesitate to respond with questions, concerns, or any other feedback.

Paweł

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Lei Zhang]

The official Valgrind bots are sticking around for now. We'll likely
retire them eventually in favor of *SAN bots. The Valgrind trybots are
slow and noisy. Most developers are better off just running Valgrind
locally.

[Paweł Hajdan, Jr.]

On Wed, Nov 19, 2014 at 2:00 AM, Matt Mueller <ma...@chromium.org> wrote:

On Tue, Nov 18, 2014 at 3:01 AM, Paweł Hajdan, Jr. <phajd...@chromium.org> wrote:

Hello Chrome developers,

to help make the Tryserver more maintainable, I'd like to remove unused and unmaintained trybots.

As part of this effort, I'd like to remove the following builders a week from now, on Nov 25:

tryserver.chromium.linux:

linux_chromeos_valgrind

linux_redux

Any update on crbug.com/359533 ?

I think it's up to developers working on openssl to add new bots. With all trybots using recipes now this should be easy. I can help if you have questions. Please see how mac_chromium_openssl_{dbg,rel} bots are set up and mirror that. Note that these bots are about to also be removed, but you'll be able to find this in version history.

FWIW I was told by Ryan this bot (linux_redux) can be removed, and as you can see from http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_redux it's 100% red. Is there any advantage of keeping it until someone has cycles to replace it?

Paweł

[Jose Torrealba]

Pardon the ignorance

I've forgotten

Who or what is  chromium-dev <chromi...@chromium.org> ?

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Paweł Hajdan, Jr.]

On Tue, Nov 18, 2014 at 7:41 PM, Ryan Tseng <hin...@chromium.org> wrote:

Sorry automate is a vague term.  I was thinking along the lines of "automatically generating a list of unused builders".

Not sure. If anyone wants to give this a try, feel free to do so. A possible challenge is that the builders are getting builds, at least occasionally. CQ has machine-readable file describing which trybots it uses, but I think we have other bots that are used just not by CQ, e.g. perf bisect bots.

I think large part here is a cleanup that wasn't done for a long time, while everyone was adding their favorite bot to humongous tryserver.chromium. Now I think we take a closer look at each newly added bot, which should help ensure they can all be maintained (using recipes also helps with that).

Paweł

 

On Tue, Nov 18, 2014 at 10:20 AM, Thiago Farina <tfa...@chromium.org> wrote:

On Tue, Nov 18, 2014 at 4:13 PM, Ryan Tseng <hin...@chromium.org> wrote:

2. We have a lot of builders, can we automate this on a dashboard?

Hum, by "automate" here, what you mean? The removal? Sorry, I couldn't get it from the context.

 

--

Thiago Farina

--
You received this message because you are subscribed to the Google Groups "infra-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infra-dev+...@chromium.org.
To post to this group, send email to infr...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/infra-dev/CAMk4ikO-vbrt9w2T%2BVTpb0riNAiPs9AhEMLH3gBWbQudRDepBQ%40mail.gmail.com.

[Ryan Tseng]

On Thu, Nov 20, 2014 at 2:33 AM, Paweł Hajdan, Jr. <phajd...@chromium.org> wrote:

On Tue, Nov 18, 2014 at 7:41 PM, Ryan Tseng <hin...@chromium.org> wrote:

Sorry automate is a vague term.  I was thinking along the lines of "automatically generating a list of unused builders".

Not sure. If anyone wants to give this a try, feel free to do so. A possible challenge is that the builders are getting builds, at least occasionally. CQ has machine-readable file describing which trybots it uses, but I think we have other bots that are used just not by CQ, e.g. perf bisect bots.

I think large part here is a cleanup that wasn't done for a long time, while everyone was adding their favorite bot to humongous tryserver.chromium. Now I think we take a closer look at each newly added bot, which should help ensure they can all be maintained (using recipes also helps with that).

I was thinking along the lines of an infra policy that "if your builder hasn't seen a job in 7 days, or a passing job in 30 days, it will be reaped."

[Paweł Hajdan, Jr.]

On Thu, Nov 20, 2014 at 7:34 PM, Ryan Tseng <hin...@google.com> wrote:

On Thu, Nov 20, 2014 at 2:33 AM, Paweł Hajdan, Jr. <phajd...@chromium.org> wrote:

On Tue, Nov 18, 2014 at 7:41 PM, Ryan Tseng <hin...@chromium.org> wrote:

Sorry automate is a vague term.  I was thinking along the lines of "automatically generating a list of unused builders".

Not sure. If anyone wants to give this a try, feel free to do so. A possible challenge is that the builders are getting builds, at least occasionally. CQ has machine-readable file describing which trybots it uses, but I think we have other bots that are used just not by CQ, e.g. perf bisect bots.

I think large part here is a cleanup that wasn't done for a long time, while everyone was adding their favorite bot to humongous tryserver.chromium. Now I think we take a closer look at each newly added bot, which should help ensure they can all be maintained (using recipes also helps with that).

I was thinking along the lines of an infra policy that "if your builder hasn't seen a job in 7 days, or a passing job in 30 days, it will be reaped."

IMHO it'd be hard to apply such a strong rule for this.

My goal isn't really to remove bots, but to ensure they are maintained, and help people do so. One way to do that is using recipes.

By the way, just a friendly reminder this first round of removals is scheduled for tomorrow. Please speak up if you rely on trybots about to be removed.

Paweł

[Dhananjay Venuri]

is there any additional documentation for chromium.linux configs as a new user to the community  I am trying to get some insight for alpha and beta builds.

[Thiago Farina]

On Mon, Nov 24, 2014 at 2:08 PM, Dhananjay Venuri <dhana...@gmail.com> wrote:

is there any additional documentation for chromium.linux configs as a new user to the community  I am trying to get some insight for alpha and beta builds.

This seems vague. What do you want to know exactly? How to build Chrome on Linux?

If it is that, please, open a new thread or search the archives of this mailing list.

--

Thiago Farina

[Paweł Hajdan, Jr.]

FWIW the change has been made (https://codereview.chromium.org/761473002/) and deployed.

Paweł