Also see http://build.chromium.org/buildbot/try-server/builders/win/builds/41761/steps/interactive_ui_tests/logs/stdio
for a similar set of failures.

I had my patch reverted due to the same issue on a waterfall win dbg bot (unable to reproduce this locally or on try bots before submission).

Scott, could you take a look? svn blames you. This is causing some redness in the tree.

Please let me know if you'd need more data, I'll try to get it.

(No comment was entered for this change.)

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=54404 

------------------------------------------------------------------------
r54404 | phajdan.jr@chromium.org | 2010-07-30 16:20:32 -0700 (Fri, 30 Jul 2010) | 10 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/browser_keyboard_accessibility_test_win.cc?r1=54404&r2=54403

GTTF: Add more logging to BrowserKeyboardAccessibility test
to help debug hangs and crashes.

Using LOG(ERROR) to make sure the output will be always
visible and captured on Windows. We need the logs. The issue
is hard to reproduce.

TEST=BrowserKeyboardAccessibility
BUG=50663
Review URL: http://codereview.chromium.org/3071011
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=54451 

------------------------------------------------------------------------
r54451 | tfarina@chromium.org | 2010-07-31 09:55:40 -0700 (Sat, 31 Jul 2010) | 15 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/app/l10n_util_unittest.cc?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/env_var.cc?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/env_var.h?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/env_var_unittest.cc?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/base/xdg_util_unittest.cc?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/locale_tests_uitest.cc?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/shell_integration_unittest.cc?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/zygote_host_linux.cc?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/plugin/plugin_main_mac.mm?r1=54451&r2=54450
   M http://src.chromium.org/viewvc/chrome/trunk/src/net/proxy/proxy_config_service_linux_unittest.cc?r1=54451&r2=54450

Reland r54418 - base: Add UnSetEnv function to EnvVarGetter API.

This reverts commit 7ed083f6d2b1b0a09c8bf9470386ba3e38f2feed.

It was reverted due to crbug.com/50663 started failing when I land this patch,
so I'm relanding it now again.

BUG=None
TEST=trybots

TBR=thestig@chromium.org

Review URL: http://codereview.chromium.org/3043018

Review URL: http://codereview.chromium.org/3076020
------------------------------------------------------------------------

Pawel, during what revisions did this start failing?

Scott, unfortunately we don't have that data. However, it seems that the tests time out and that timeout triggers the assertion failure. We should probably CC or maybe even assign to test authors for more investigation.

By the way, I have recently added logging to the test which seems to flake most often. That should give us more info.

(No comment was entered for this change.)

As far as I can tell this bug is no longer relevant. All the autocomplete tests are no longer marked as flakey, and there are specific bugs filed for BrowserFocusTest.TabsRememberFocus and FindInPageTest.PrepopulateRespectBlank .

In try bot run

http://build.chromium.org/buildbot/try-server/builders/win/builds/41841/steps/interactive_ui_tests/logs/stdio

There were a series of failures (unrelated to the code being tested) that resulted from the following assertion tripping:

]118056:118060:0726/220734:9055359:FATAL:ui_controls_win.cc(84)] Check failed: !installed_hook_. 

The backtrace for this assertion was:


	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x01518CB1+18294097]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x014E7DE1+18093697]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x0040EB41+426977]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x0040ECC2+427362]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x0040EF90+428080]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x0040FA89+430889]
	(No symbol) [0x003101D8]
	(No symbol) [0x00313A7C]
	(No symbol) [0x00316111]
	(No symbol) [0x002CC3C7]
	(No symbol) [0x002DB34C]
	(No symbol) [0x002D97C1]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x003A8290+6960]
	(No symbol) [0x002CA36B]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x0185C8A3+21717315]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x0185D5B3+21720659]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x0185DB51+21722097]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x01862AD2+21742450]
	RelaunchChromeBrowserWithNewCommandLineIfNeeded [0x01861736+21737430]
	(No symbol) [0x002E3F8E]
	(No symbol) [0x002E3AD7]
	(No symbol) [0x0035847C]
	BaseThreadInitThunk [0x7744ECCB+14]
	RtlCreateUserProcess [0x77C1D24D+140]
	RtlCreateProcessParameters [0x77C1D45F+78]

This caused the failure of the following tests:

BrowserFocusTest.TabsRememberFocus
AutocompleteEditViewTest.BackspaceInKeywordMode
AutocompleteEditViewTest.Escape
AutocompleteEditViewTest.DesiredTLD
AutocompleteEditViewTest.EnterToSearch
AutocompleteEditViewTest.EnterToOpenHistoryPage
AutocompleteEditViewTest.EscapeToDefaultMatch
FindInPageTest.PrepopulateRespectBlank

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

(No comment was entered for this change.)