Commit c73d00e4 authored by David Bertoni's avatar David Bertoni Committed by Commit Bot

[Extensions] Re-enable a test on Windows.

The EventsApiTest.NewlyIntroducedListener test isn't flaky on
Windows, although it still flakes on other platforms.

Bug: 833854
Change-Id: Ib524f61b79d6ae83c1e7e39c63c0522429a3f118
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2139450Reviewed-by: default avatarKelvin Jiang <kelvinjiang@chromium.org>
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#758900}
parent 1e9209f7
......@@ -208,10 +208,16 @@ IN_PROC_BROWSER_TEST_F(EventsApiTest,
}
}
// Disabled due to flaky timeouts. https://crbug.com/833854
// This test is OK on Windows, but times out on other platforms.
// https://crbug.com/833854
#if defined(OS_WIN)
#define MAYBE_NewlyIntroducedListener NewlyIntroducedListener
#else
#define MAYBE_NewlyIntroducedListener DISABLED_NewlyIntroducedListener
#endif
// Tests that if an extension's updated version has a new lazy listener, it
// fires properly after the update.
IN_PROC_BROWSER_TEST_F(EventsApiTest, DISABLED_NewlyIntroducedListener) {
IN_PROC_BROWSER_TEST_F(EventsApiTest, MAYBE_NewlyIntroducedListener) {
std::vector<ExtensionCRXData> data;
data.emplace_back("v1");
data.emplace_back("v2");
......
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