PSA: More mash_browser_tests are coming to the Chrome OS bots

[James Cook]

Tomorrow I will land a CL that changes the test filter file for mash_browser_tests from a whitelist to a blacklist. This only affects the linux-chromeos bots. The mojo FYI bot has been using this blacklist for a while now and the suite is stable. I wanted to let everyone know because this will add a large number of tests to the suite (~8000). If you see flake, ping me or revert the CL.

Chrome OS developers: mash_browser_tests runs browser_tests --mash (a flag that runs the ash window manager and system UI in a separate process). See go/mustash or //ash/README.md for details. If your CL breaks a test in this suite it is probably because your code is trying to access code in //ash directly from the browser process. That won't work under --mash; you'll need to use the mojo IPC interfaces in //ash/public/interfaces or add a new mojo interface for your feature.

Thanks,

James