I didn't set up the bots, but I recently read a bug and have some of the history of the waterfall in my head. The bots weren't initially swarmed and they used to have bare metal builders for speed, as well as more testers. We later enabled swarming and switched to VMs to reclaim the bare metal machines, leaving a single tester, that still have "(1)" in its name.

Mac and ChromeOS only have a single tester, but Linux has 2 and they use the same binary but test different configs. Is that a good enough reason to keep the builder + 2 tester setup, or should we just switch to 2 builder-testers?

Re the history part, yep that was me who did that.

I meant combining all the builders and testers for each config. i.e. chromium.memory would just have 3 columns: linux, mac, chromeos.

If we can merge the tests running on "Linux ASan LSan Tests (1)" with the ones running on "Linux ASan Tests (sandboxed)", then we can go down to a single Linux bot.

Yes that should be possible. AFAIK the only difference between the two testers is that the LSan one species the command line argument of "--lsan=1". That can be specified in the chromium.memory.json file in the "args" section inside "gtest_tests".

maruel@ has been thinking about this problem recently.

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.

Available, but no owner or component? Please find a component, as no one will ever find this without one.