Commit 2fcc6147 authored by Wez's avatar Wez Committed by Commit Bot

Revert "Disable test that should be using the new API QuitClosure"

This reverts commit 5e0c2251.

Reason for revert: This test will now be fixed as part of re-landing the QuitCurrent*Deprecated() cleanup.

Original change's description:
> Disable test that should be using the new API QuitClosure
> 
> TBR=wez@chromium.org
> NOTRY=True
> 
> Bug: 859151
> Change-Id: Id45c6e679ea50523e99a72cf9ae52a7bd1254286
> Reviewed-on: https://chromium-review.googlesource.com/1121631
> Reviewed-by: Yi Gu <yigu@chromium.org>
> Commit-Queue: Yi Gu <yigu@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#571755}

TBR=wez@chromium.org,yigu@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 859151
Change-Id: I94df8df53bc4f58a9c676365db997ab920aa811d
Reviewed-on: https://chromium-review.googlesource.com/1122937Reviewed-by: default avatarWez <wez@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571977}
parent 4df6a477
...@@ -134,9 +134,8 @@ class DistillablePageUtilsBrowserTestOption : public InProcessBrowserTest { ...@@ -134,9 +134,8 @@ class DistillablePageUtilsBrowserTestOption : public InProcessBrowserTest {
using DistillablePageUtilsBrowserTestAlways = using DistillablePageUtilsBrowserTestAlways =
DistillablePageUtilsBrowserTestOption<kAlwaysTrue>; DistillablePageUtilsBrowserTestOption<kAlwaysTrue>;
// This test should be updated to use QuitClosure. See crbug.com/859151.
IN_PROC_BROWSER_TEST_F(DistillablePageUtilsBrowserTestAlways, IN_PROC_BROWSER_TEST_F(DistillablePageUtilsBrowserTestAlways,
DISABLED_TestDelegate) { TestDelegate) {
for (unsigned i = 0; i < sizeof(kAllPaths) / sizeof(kAllPaths[0]); ++i) { for (unsigned i = 0; i < sizeof(kAllPaths) / sizeof(kAllPaths[0]); ++i) {
testing::InSequence dummy; testing::InSequence dummy;
EXPECT_CALL(holder_, OnResult(true, true, _)) EXPECT_CALL(holder_, OnResult(true, true, _))
......
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