Win Asan Release is on the (misnamed) lkgr waterfall. We probably want to add a win/asan bot to the memory waterfall instead and add an (opt-in) trybot mirroring that.
dpranke, do I need anyone (you?) to approve adding a win/asan bot to chromium.memory? If adding it is fine, should the bot use a builder/tester split like the other memory bots, or just build and swarm on one machine? Probably the latter?
You are welcome to add bots to that waterfall.
(You need OWNERS of //testing/buildbot and //infra/config to approve adding things, obviously. Mostly that's members of Infra>Client>Chrome or myself for ops-side approval. Sometimes you also need src-side, like kbr@ for .gpu or lexan folks for .clang. .memory doesn't really have any relevant stakeholders).
The reasons to do a builder/tester split are:
1) You need to build once but run the binaries on different os/hardware configs, and you want to see the results of each config as a separate builder
2) You want the slightly faster cycle times you get for pipelining build + test on two different builders
3) You want to be able to separate out compile failures from build failures more easily and potentially get smaller build ranges for compile failures.
I expect you don't really care about any of these, and so should stick with a single builder for simplicity.
Also, please follow bit.ly/chromium-build-naming if possible to pick the name, so something like 'win-asan-release' instead of 'Win ASan Release'.
The naming standards are flawed but we're trying to follow them where we can when adding new builders, even if that means that things on a given waterfall will be inconsistently named for a while.
FYI, issue 871761 - the bot probably shouldn't have been added to the main console until fully debugged, as it's confusing to sheriffs.
If you're following instructions from some LUCI / Infra doc, it would help to get it updated to avoid this issue in the future. Thanks!
Status:
- There's a win-asan bot on chromium.memory and on the memory subconsole on the main waterfall
- There's a matching win-asan bot that does the same thing
- Right now, these only build and don't run tests. https://chromium-review.googlesource.com/c/chromium/src/+/1179087 tries to add them, but atm a bunch of tests are red. I'm adding blockers for these
That's the main waterfall asan bot, visible on build.chromium.org and on the chromium.memory waterfall. There's a matching win-asan trybot at https://ci.chromium.org/p/chromium/builders/luci.chromium.try/win-asan that can be triggered through the usual CHOOSE TRYBOTS gerrit ui, or via `it cl try -B luci.chromium.try -b win-asan`. (It's backed by a single bot, so if lots of people use it maybe we'll have to give it more hardware.)
Comment 1 by thakis@chromium.org
, Aug 1