diff options
| author | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-04-05 16:59:56 +0000 |
|---|---|---|
| committer | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-04-05 16:59:56 +0000 |
| commit | 3cfa2facc0fc69dda97d470e08a83ffa5a183f9a (patch) | |
| tree | 760f7a280888360af661ecf93d89b9d076695a54 /ui | |
| parent | 5208144733d893b2411757a14c4599184e021c7e (diff) | |
| download | chromium_src-3cfa2facc0fc69dda97d470e08a83ffa5a183f9a.zip chromium_src-3cfa2facc0fc69dda97d470e08a83ffa5a183f9a.tar.gz chromium_src-3cfa2facc0fc69dda97d470e08a83ffa5a183f9a.tar.bz2 | |
Renable the ProtocolHandlerRegistry tests on Windows. I tracked down the dcheck (not finding an installer string in browser_tests binary) to the fact that we were registering the protocol handler with the OS. It happened on the bots but not locally because it needs Chrome to be running as an admin. I have no idea why this only crashes on my new test but not the existing one on the bots, since locally they both hit the assert when running as an admin.
Review URL: https://chromiumcodereview.appspot.com/9998002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130949 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui')
0 files changed, 0 insertions, 0 deletions