New issue
Advanced search Search tips

Issue 769892 link

Starred by 0 users

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

buildbucket plugin groups builders in different buckets

Project Member Reported by aga...@chromium.org, Sep 28 2017

Issue description

See https://webrtc-review.googlesource.com/c/src/+/1576/1 and https://screenshot.googleplex.com/S4bftcPJr3t

The red build in the background is http://build.chromium.org/p/tryserver.webrtc/builders/android_compile_rel/builds/1234 on tryserver.webrtc

The yellow build in the foreground is https://build.chromium.org/p/tryserver.chromium.android/builders/android_compile_rel/builds/1081 on tryserver.chromium.android

These are different builders on different masters that just happen to have the same name. The build grouping used to take into account bucket names; I thought it still did, but apparently it isn't working right.
 

Comment 1 by no...@chromium.org, Sep 28 2017

neither gerrit nor rietveld ever grouped by bucket
https://chromium.googlesource.com/infra/gerrit-plugins/buildbucket/+/db22171e3536f79696753cc3f241d82758e28c05/src/main/resources/static/cr-buildbucket-view.js#166

there needs to be a discussion/design first. Is this a new builder? It is not obvious what to do with such builders, e.g. how to display blocks of builds. Display "<bucket>:<builder>" of "<builder>" for non-unique builders?


Comment 2 by aga...@chromium.org, Sep 28 2017

Cc: no...@chromium.org
Owner: ----
Status: Available (was: Assigned)
Huh, looks like you're right. Not sure why I thought the old version did group by bucket as well.

This is not a new builder, it's a builder that's been around for a long time. WebRTC runs both their own tryjobs and chromium tryjobs; they just happen to have some bots with the same names.

Turns out Rietveld handles this even worse. If you try to run an "android_compile_rel" job on https://codereview.chromium.org/3010363002, there are three options (on luci.webrtc.try, master.tryserver.webrtc, and master.tryserver.chromium.android) but it is impossible to select only one of them, and it ends up just triggering a single job on tryserver.webrtc (no idea how/why it picked that one).

Comment 3 by no...@chromium.org, Feb 22 2018

Status: Archived (was: Available)

Sign in to add a comment