New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 697560 link

Starred by 1 user
Status: Fixed
Owner:
█ dimaa@chromium.org
Last visit > 30 days ago
Closed: Mar 2017
Cc:
█ phajdan.jr@chromium.org
sadrul@chromium.org
█ bruthig@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

BrowserThreadTest tests are flaky

Project Member Reported by sadrul@chromium.org, Mar 1 2017 
BrowserThreadTest tests are currently flaky. Most of these tests always fail (crash) the first time, and need to be retried separately.
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 2 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/61c9b8f29a2a7815f57b429725ce34922a828305

commit 61c9b8f29a2a7815f57b429725ce34922a828305
Author: dimaa <dimaa@chromium.org>
Date: Thu Mar 02 18:51:50 2017

Most of BrowserThreadTest tests always fail (crash) the first time, and need to be retried separately (each test isolated).

BrowserThreadImpl states need to be cleaned up between tests,
otherwise the subsequent tests will crash trying to reinitialize BrowserThreadImpl.

This CL make sure that this is done correctly.
BUG= 697560 

Review-Url: https://codereview.chromium.org/2721223004
Cr-Commit-Position: refs/heads/master@{#454321}

[modify] https://crrev.com/61c9b8f29a2a7815f57b429725ce34922a828305/content/browser/browser_thread_unittest.cc

Comment 2 by sadrul@chromium.org, Mar 3 2017

Status: Fixed (was: Available)
►

Sign in to add a comment