is chromium.chromiumos waterfall coverage in scope for code yellow?

[Paweł Hajdan, Jr.]

I'm looking at https://code.google.com/p/chromium/issues/detail?id=429025 which is about CQ coverage for chromium.chromiumos waterfall.

Do we consider that in scope for the code yellow? AFAICT chromium.chromiumos is not on build.chromium.org, so it's probably not "main waterfall".

For now the bots have only been added to the tryserver, which I think is fine - it sounds reasonable to provide optional tryserver coverage for any buildbot master we have. *_ng bots actually make this super-easy (see https://codereview.chromium.org/691293002).

I'm not sure however if we should proceed with adding the new builders to the CQ. Even if we have some capacity on Linux now, I'd prefer to keep the option of kicking out non-essential builders when we do need it.

Should https://code.google.com/p/chromium/issues/detail?id=429025 block the "CQ matches main waterfall" tracking bug? I conservatively made it a blocker so it's easier to look up, but during a deeper review I realized the buildbot master it mentions doesn't seem to be on main waterfall.

Paweł

[Daniel Jacques]

These builds, specifically, are Chromum-for-Linux (ChromiumOS variant) builds, not true ChromiumOS builds - that is, they are a Linux build with the "chromeos=1" GYP flag enabled.

Central to this topic is the idea of the "main waterfall". Alternative options to excluding this set of builders are either to expand the scope of "main waterfall" to include the builders on "chromium.chromiumos" or to relocate these builders onto the main waterfall.

-Dan

[Dirk Pranke]

Are we talking about http://build.chromium.org/p/chromium.chromiumos/console ? It shows up in the header at the top of build.chromium.org, just like Mac, Win, and Linux.

 

I don't know why it wouldn't be in scope, or why it would be any different from the other platforms.

-- Dirk

--
You received this message because you are subscribed to the Google Groups "Chromium Hackability Code Yellow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hackability-c...@chromium.org.
To post to this group, send email to hackabi...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/hackability-cy/CAD1RUU9sYKY8c4KpKCtn2fSDB%2BSEjYLqHm%3Dikz_%2BKZ%2B-17B6AQ%40mail.gmail.com.

[Paweł Hajdan, Jr.]

Indeed, thanks for catching my mistake.

Yay, so we're actually making progress here - Daniel, do you plan to add the new trybots to CQ experiment?

Paweł

[Daniel Jacques]

I think it's a good idea. They should be pretty cheap time-wise, and based on previous discussions with sergeyberezin@ we should have capacity.

-Dan

[Daniel Jacques]

Pardon, I would only want to add the debug build (compile-only) of this bot set. The release build is already represented with a builder/tester.

-Dan

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