Issue 16018011: Revert "Shouldn't access LayerTreeTest::layer_tree_host on impl thread"

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 16018011: Revert "Shouldn't access LayerTreeTest::layer_tree_host on impl thread" (Closed)

Created:
7 years, 6 months ago by Xianzhu

Modified:
7 years, 6 months ago

Reviewers:
Ian Vollick

CC:
chromium-reviews, cc-bugs_chromium.org

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

Visibility:
Public.

More Reviews

Description

Revert "Shouldn't access LayerTreeTest::layer_tree_host on impl thread" This reverts commit 1675fd684187bea60094441e2d0406057f6adbee. It causes DCHECK failure on an Android bot. BUG=235188 TBR=vollick Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=202975

Patch Set 1 #

Created: 7 years, 6 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+19 lines, -11 lines)			Patch
M	cc/test/layer_tree_test.h	View	1 chunk	+1 line, -1 line	0 comments	Download
M	cc/test/layer_tree_test.cc	View	1 chunk	+0 lines, -5 lines	0 comments	Download
M	cc/trees/layer_tree_host_unittest_animation.cc	View	4 chunks	+14 lines, -3 lines	0 comments	Download
M	cc/trees/single_thread_proxy.cc	View	2 chunks	+4 lines, -2 lines	0 comments	Download

Messages

Total messages: 1 (0 generated)

Expand Messages | Collapse Messages

Xianzhu

7 years, 6 months ago (2013-05-29 21:25:23 UTC) #1

Message was sent while issue was closed.

Committed patchset #1 manually as r202975 (presubmit successful).

Expand Messages | Collapse Messages