Issue 475063002: Remove no-op FLAKY_ prefix from BrowsingDataRemovalMask test

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 475063002: Remove no-op FLAKY_ prefix from BrowsingDataRemovalMask test (Closed)

Created:
6 years, 4 months ago by adamk

Modified:
6 years, 4 months ago

Reviewers:
ojan

CC:
chromium-apps-reviews_chromium.org, chromium-reviews, extensions-reviews_chromium.org

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Project:
chromium

Visibility:
Public.

Remove no-op FLAKY_ prefix from BrowsingDataRemovalMask test This prefix was added in https://src.chromium.org/viewvc/chrome?revision=207246&view=revision, and even then it was a no-op. Despite the no-op-ness, the test flakiness was fixed over a year ago (see bug). Now the prefix serves only to it only serves to confuse sheriff-o-matic. BUG=251742 TBR=ojan@chromium.org NOTRY=true Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=289631

Created: 6 years, 4 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -1 line)			Patch
	M	chrome/browser/extensions/api/browsing_data/browsing_data_test.cc	View		1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 3 (0 generated)

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/adamk@chromium.org/475063002/1

6 years, 4 months ago (2014-08-14 16:39:58 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (1) as 289631