Comment #2 on issue 28629 by [email protected]: We need a way to
reliably tell gtk widget state on x11 to make tests more reliable
http://code.google.com/p/chromium/issues/detail?id=28629
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=33068
------------------------------------------------------------------------
r33068 | [email protected] | 2009-11-25 08:08:59 -0800 (Wed, 25 Nov 2009)
| 8 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ssl/ssl_browser_tests.cc?r1=33068&r2=33067
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/find_bar_host.cc?r1=33068&r2=33067
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/find_bar_host_browsertest.cc?r1=33068&r2=33067
Moving two tests to FLAKY tests.
TestHTTPSErrorWithNoNavEntry: fails differently on 32 and 64 bits due to
timing issue. (We thought it's deterinistic, but this is apparently not)
FindDisappearOnNavigate: due to asynchronous-ness on x11.
BUG=28629,28098
TEST=build and run browser_tests in 64bit.
Review URL: http://codereview.chromium.org/438010
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
