diff options
author | finnur@chromium.org <finnur@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-20 14:05:27 +0000 |
---|---|---|
committer | finnur@chromium.org <finnur@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-09-20 14:05:27 +0000 |
commit | 799f9fbfa3dbb22d85f4be811e733e8809154c98 (patch) | |
tree | 6d5dde0170cb6362df29b7193ebfc3abd75c2f4c /webkit | |
parent | 837018e189f596c566c28a459ba52f926586288e (diff) | |
download | chromium_src-799f9fbfa3dbb22d85f4be811e733e8809154c98.zip chromium_src-799f9fbfa3dbb22d85f4be811e733e8809154c98.tar.gz chromium_src-799f9fbfa3dbb22d85f4be811e733e8809154c98.tar.bz2 |
Updating status on three tests:
Someone changed FindInPagePrematureEnd from DISABLED to FAILS. However, it is not expected to pass until we fix 11761 so we don't need to run it until then. Marking it back as DISABLED.
NoIncognitoPrepopulate was failing because the infrastructure was laggy (the simple act of launching a page in incognito could take up to a minute). I can no longer repro the error, so I think the problem is gone.
Back in June, ActivateLinkNavigatesPage got marked as DISABLED (because it crashed occasionally), with a bug filed against no-one, so I have no crashdump or try bot logs nor any idea what the state of it is. Marking as enabled to see if it is still a problem. It passes locally.
BUG=45594, 40948
TEST=These are tests.
Review URL: http://codereview.chromium.org/601044
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@59930 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit')
0 files changed, 0 insertions, 0 deletions