Where did you the LUCI builds shown https://ci.chromium.org/p/chromium/g/main/console ?
(screenshot would be nice)

To my best knowledge it still shows only buildbot ones, but it's possible we've messed something up.

+jchinlee@ who is currently in early stages of migrating builder to LUCI.

IIUC this is just in the console header. The builder is not fully migrated yet; perhaps it'd be less confusing to remove the builder from the header. I'll put something together for that.

+nodir@

Oh, I didn't think about the header. Good point - I think header should use the same logic as console column to display latest prod build from whichever builders are configured for it.

Pri1 because this is blocking migrations.

the problem seems to be stemming from the fact that we are using def.Builders instead of def.Def.Builders in https://cs.chromium.org/chromium/infra/go/src/go.chromium.org/luci/milo/buildsource/console.go?q=console.go+&sq=package:chromium&l=167
and thus flatten the list of builder ids (we should not)

I believe +iannucci has most context

Removing from sheriff-queue, as I don't think there is anything for sheriffs to do here.

When I filed the bug, both luci and buildbot builds were shown in the chromium.win/debug/builder/32 column, which was quite confusing as successful and non successful builds alternated. 
Now only the header seems to be affected.

Marked as dup

Marked as dup

Not a dupe! This is specificially about the console headers, not the console view (which we don't have enough info for yet).

So what's happening is that the console header-rendering code operates differently from the console rendering code. It should be pretty easy to make them behave identically.

We have been looking at this actively and have seen this recently. dullweber@chromium.org if you see this again, please let us know.