Issue 2190863002: Revert changes to device/test/run_all_unittests.cc

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 2190863002: Revert changes to device/test/run_all_unittests.cc (Closed)

Created:
4 years, 4 months ago by tsergeant

Modified:
4 years, 4 months ago

Reviewers:
mcasas, Paul Stewart

CC:
chromium-reviews, chrome-apps-syd-reviews_chromium.org

Base URL:
https://chromium.googlesource.com/chromium/src.git@2810

Target Ref:
refs/pending/branch-heads/2810

Project:
chromium

Visibility:
Public.

Revert changes to device/test/run_all_unittests.cc Changes to this file were made in https://codereview.chromium.org/2185993003/. However, they were not reverted when the remainder of that patch was reverted in https://codereview.chromium.org/2188933002/. This should fix the Android build. TBR=pstew@chromium.org,mcasas@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=612334, 632239 Review-Url: https://codereview.chromium.org/2185303002 Cr-Commit-Position: refs/heads/master@{#408310} (cherry picked from commit 77d0c290852d4d0042ec117ca28592b77c084729)

Created: 4 years, 4 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+0 lines, -2 lines)			Patch
	M	device/test/run_all_unittests.cc	View		2 chunks	+0 lines, -2 lines	0 comments	Download

Total messages: 1 (0 generated)

tsergeant

4 years, 4 months ago (2016-07-28 05:24:30 UTC) #1

Message was sent while issue was closed.

Something went wrong while landing this and the CL didn't update, but it -did-
successfully land as 7212bbc083ff30c65ffa5ca0333f73f0b63221a3.