site-per-process has been the default for more than a week now (see issue 824966 and r552589). Therefore Site Isolation Linux seems redundant now. Site Isolation Win bots might also be redundant, but we might want to consider the following before turning it down:
- browser_tests, unit_tests and interactive_ui_tests, etc. have site-per-process coverage on the main waterfall. not_site_per_process versions of these test suites are run on linux_chromium_rel_ng. QUESTION: do we care about not_site_per_process_xxx on Windows?
- content_browsertests, content_unittests, layout tests, etc. have site-per-process coverage on linux_chromium_rel_ng. QUESTION: do we care about site-per-process coverage of these test suites on Windows?
Comment 1 by creis@chromium.org
, May 1 2018