Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(125)

Issue 2176803002: Fix flaky MetricsWebContentsObserverBrowserTests (Closed)

Created:
4 years, 5 months ago by Bryan McQuade
Modified:
4 years, 5 months ago
Reviewers:
Charlie Harrison
CC:
chromium-reviews
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Fix flaky MetricsWebContentsObserverBrowserTests This reverts commit 58ac1adec45fcd08d91d2c09e0b2c17ed3d181cf, which disabled a few flaky tests, and fixes those tests so they are no longer flaky. In a follow up change, we'll roll back https://codereview.chromium.org/2172183002 since this change addresses the flakes caused by that patch. BUG=630549 Committed: https://crrev.com/810c47d4645d63abbda6bbdc11b617115d755bd6 Cr-Commit-Position: refs/heads/master@{#407260}

Patch Set 1 #

Patch Set 2 : switch to about:blank #

Unified diffs Side-by-side diffs Delta from patch set Stats (+19 lines, -31 lines) Patch
M chrome/browser/page_load_metrics/page_load_metrics_browsertest.cc View 1 13 chunks +19 lines, -31 lines 0 comments Download

Messages

Total messages: 18 (10 generated)
Bryan McQuade
PTAL
4 years, 5 months ago (2016-07-22 19:28:20 UTC) #4
Charlie Harrison
LGTM!
4 years, 5 months ago (2016-07-22 20:12:18 UTC) #5
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2176803002/20001
4 years, 5 months ago (2016-07-22 20:58:45 UTC) #12
commit-bot: I haz the power
Committed patchset #2 (id:20001)
4 years, 5 months ago (2016-07-22 21:03:44 UTC) #13
commit-bot: I haz the power
Patchset 2 (id:??) landed as https://crrev.com/810c47d4645d63abbda6bbdc11b617115d755bd6 Cr-Commit-Position: refs/heads/master@{#407260}
4 years, 5 months ago (2016-07-22 21:05:46 UTC) #15
Charlie Harrison
Do you know why the tests were failing without about:blank?
4 years, 5 months ago (2016-07-22 21:10:28 UTC) #16
Bryan McQuade
Not sure. Seems specific to Windows, 4 for 4 failures. Perhaps we have special handling ...
4 years, 5 months ago (2016-07-22 21:14:57 UTC) #17
Charlie Harrison
4 years, 5 months ago (2016-07-22 21:16:04 UTC) #18
Message was sent while issue was closed.
It's possible. I think a race condition might be more likely, as about:blank has
special semantics (it's synchronous, for one).

Powered by Google App Engine
This is Rietveld 408576698