Remove cros_browser_sanity_test from all CrOS bots.
This suite was useful when we were first spinning up tests on CrOS, as it provides a smoke check of the browser. Since then, we've also integrated Tast tests. And as more Tast tests have been written, they've grown to provide coverage of everything that the sanity test provided. (eg: tests like ui.ChromeLogin check the browser's log in flow, arc.* tests cover ARC functionality.) These days, you'll never see the sanity test fail without also seeing at least one Tast test failing. Bug: None Change-Id: I2a7db54bec15eac7bf909970cdf21946a306817b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518661 Commit-Queue: Ben Pastene <bpastene@chromium.org> Reviewed-by:Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/master@{#824084}
Showing
Please register or sign in to comment