Ensure capacity for 8000 more tests in mash_browser_tests suite |
|||||
Issue descriptionI want to 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. This suite has been stable on the mojo FYI bot for a while now. It will increase the number of tests in this suite from ~700 to ~8000. https://chromium-review.googlesource.com/c/chromium/src/+/895906 Background: mash_browser_tests runs browser_tests --mash (a flag that runs the ash window manager and system UI out of the browser process). See go/mustash or //ash/README.md for details. I want to make sure we have capacity to handle the increase in tests.
,
Feb 1 2018
I think this'll probably cost us another ~400 cores at peak, and we're redlining on capacity now. smut@, can we add that? +jbudorick, fyi Also, I'm adding the "Build-Capacity" label for this. Maybe we can start using that to track capacity/growth requests? I'm open to other suggestions for how to do this.
,
Feb 1 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/infradata/config/+/887e54a2f2d746d741f7e7519d19b45102c82318 commit 887e54a2f2d746d741f7e7519d19b45102c82318 Author: smut <smut@google.com> Date: Thu Feb 01 00:36:01 2018
,
Feb 3 2018
,
Feb 21 2018
These tests have been running on the main waterfall for a week, so I'm guessing this happened.
,
Jul 26
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jamescook@chromium.org
, Jan 31 2018Cc: sky@chromium.org