Issue 4841002: Disable FindInPageTest.PrepopulateRespectBlank

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 4841002: Disable FindInPageTest.PrepopulateRespectBlank (Closed)

Created:
10 years, 1 month ago by Paweł Hajdan Jr.

Modified:
9 years, 7 months ago

Reviewers:
Finnur

CC:
chromium-reviews, ben+cc_chromium.org, Paweł Hajdan Jr.

Visibility:
Public.

Description

Disable FindInPageTest.PrepopulateRespectBlank TBR=finnur BUG=62937 TEST=interactive_ui_tests Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=65927

Patch Set 1 #

Created: 10 years, 1 month ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+2 lines, -1 line)			Patch
	M	chrome/browser/ui/views/find_bar_host_interactive_uitest.cc	View		1 chunk	+2 lines, -1 line	0 comments	Download

Messages

Total messages: 3 (0 generated)

Expand Messages | Collapse Messages

Finnur

I'm really disappointed with the level of detail here. The description of this changelist says ...

10 years, 1 month ago (2010-11-12 11:06:05 UTC) #2

Paweł Hajdan Jr.

10 years, 1 month ago (2010-11-12 11:09:11 UTC) #3

On Fri, Nov 12, 2010 at 12:06, <finnur@chromium.org> wrote:

> I remember in the past that the machines running interactive tests needed
> to be
> rebooted sometimes because they got wedged somehow. Have we investigated
> whether
> rebooting takes care of this problem, instead of just disabling tests?

This is from a scheduled Windows tryserver run. Afaik tryservers are
rebooted between each run.

I'm sorry about the useless log. I'd suggest adding some debugging info and
re-enabling the test.

Expand Messages | Collapse Messages