commit 9e20e8d054094d786d19602c3f2ff031264c0801
author Dirk Pranke <dpranke@chromium.org> Mon Jun 18 02:46:54 2018
committer Commit Bot <commit-bot@chromium.org> Mon Jun 18 02:46:54 2018
tree 82d647a657efb17d873c4c3bb829bbd88b51349f
parent b879ee4c2ab27cb48a4ccb3f335d78142d42a297

Reenable browser_tests on chromium.mac in quarantine pool.

This re-enables just the browser_tests suite on the
chromium.mac bots and the matching trybots. The tests
on Mac10.13 Tests are still marked as experimental, so
failures there won't block the CQ. The re-enabled tests
will run in the 'Chrome-quarantine' pool, which means
that if the tests kill the machines, it should only
affect the machines in that pool, and not the machines
in the main 'Chrome' pool.

The tests are still disabled on chromium.clang, chromium.fyi,
and chromium.memory, and viz_browser_tests and
surface_sync_browser_tests are still disabled everywhere.

If it looks like this approach is working, we can reenable
those as well as long as they go into the quarantine pool.

R=jbudorick@chromium.org
BUG=828031
NOTRY=true

Change-Id: I2e914b68584fd4d718aba246906f38b0724a08f1
Reviewed-on: https://chromium-review.googlesource.com/1103796
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567922}