Fix how --gtest_filter interacts with PRE_ tests

BUG=371785
R=sky@chromium.org

Review URL: https://codereview.chromium.org/445953002

Cr-Commit-Position: refs/heads/master@{#288298}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@288298 0039d316-1c4b-4281-b951-d872f2087c98
parent b3f957e6
...@@ -805,6 +805,9 @@ void TestLauncher::RunTests() { ...@@ -805,6 +805,9 @@ void TestLauncher::RunTests() {
continue; continue;
} }
if (!launcher_delegate_->ShouldRunTest(test_case, test_info))
continue;
// Skip the test that doesn't match the filter (if given). // Skip the test that doesn't match the filter (if given).
if (!positive_test_filter_.empty()) { if (!positive_test_filter_.empty()) {
bool found = false; bool found = false;
...@@ -828,9 +831,6 @@ void TestLauncher::RunTests() { ...@@ -828,9 +831,6 @@ void TestLauncher::RunTests() {
if (excluded) if (excluded)
continue; continue;
if (!launcher_delegate_->ShouldRunTest(test_case, test_info))
continue;
if (base::Hash(test_name) % total_shards_ != if (base::Hash(test_name) % total_shards_ !=
static_cast<uint32>(shard_index_)) { static_cast<uint32>(shard_index_)) {
continue; continue;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment