summaryrefslogtreecommitdiffstats
path: root/ui/base/cursor/cursor_loader_win.h
diff options
context:
space:
mode:
authorjam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-09-11 20:15:53 +0000
committerjam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-09-11 20:15:53 +0000
commitff8e80ecc662d9b2959881276393e9710ca875e2 (patch)
tree4d38c70902476c6e7272d88ecc9b672edf1f49c8 /ui/base/cursor/cursor_loader_win.h
parent2c97de39ad7fdd1f923e4b26d29ddd5ce82b3464 (diff)
downloadchromium_src-ff8e80ecc662d9b2959881276393e9710ca875e2.zip
chromium_src-ff8e80ecc662d9b2959881276393e9710ca875e2.tar.gz
chromium_src-ff8e80ecc662d9b2959881276393e9710ca875e2.tar.bz2
Allow running browser tests each in single-process mode. This is useful for Android team, which want to run every test in content_browsertests in single-process mode. Browser tests need to run in separate processes though, each since browser initialization can't happen twice.
Currently, if --single-process is specified, the second test run will assert because of the multiple browser-process initialization problem. This change makes it so that it works as expected. However, it will still fail as before if --single-process and --gtest_filter=<multiple_tests> is passed. Review URL: https://codereview.chromium.org/10928114 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156107 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/base/cursor/cursor_loader_win.h')
0 files changed, 0 insertions, 0 deletions