I don't know anything about legoland. The go link is broken.

betty-vmtest-informational has nothing to do with constables. It is an experiment to run CTS in a VM.

I just populated the go link. Legoland lets you see groups of builders with a short history. 

Hmm, the link works for me (although it's a little slow to load).

ihf@ - Who should be monitoring this builder? (Also, what is CTS?)

PoHsien and I look at the builder at times (low priority atm but will come back). CTS is the Android Compatibility Test Suite.

dgarret@ - How about we create a chrome-informational group for gardening and leave betty-vmtest-informational where it is, i.e. in Other > informational ?

Sorry, this is correct: go/legoland-gardener

Or just: go/legoland

ihf@ Please do take a look at Legoland. It's the new build UI, and builds have already started migrating from the old one.

stevenjb@ we have a bug to move the informational label to the Chrome PFQ tab. I'd rather do that, then move the betty builder to a new label, mostly because it's still on buildbot, and thus visible even if the label isn't in Legoland yet.

I could reuse "utility" for betty, but that seems wrong.

I think we should add a new label, but I'm not sure what it should be. I hate to have "misc". "Experimental" is a bit overloaded since it wouldn't be used for builders that are in the CQ/PFQs but unimportant.

The UI looks great. Thanks for bringing it here. 
I have no strong feeling about the name or labels. We can use existing betty-incremental for monitoring purpose instead.

'misc' for betty? 'android-informational'?

It seems unfortunate that renaming a label is a chore. "informational" is pretty generic, "chrome-informational" would be better IMO regardless of where the label is grouped. *shrug*. As long as we have a label that reserved for informational builders that gardeners need to pay attention to, I don't have a strong opinion.

The problem is that they are recorded write only when a build is created, so build history gets weird if you change them.

I think in this case "android-something" and putting it next to the Android PFQ makes sense. However, the meaning is different. This builder tests the ARC already in ChromeOS, while the Chrome informationals test Chrome that hasn't reached ChromeOS yet.

android-validation ?

I need to do this in the next few days, not a fixit.

We ended up creating "chrome_informational" and putting those builders next to the Chrome PFQ, while leaving the remaining "informational" builders alone.