summaryrefslogtreecommitdiffstats
path: root/chrome/browser/process_singleton_linux.cc
diff options
context:
space:
mode:
authorjam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-08-04 05:13:10 +0000
committerjam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-08-04 05:13:10 +0000
commitfe63292b5ff8a734578877d192c7f89aa3845e87 (patch)
treef6cdd238dc2dfe12f8e19032a2239c0185bf6ce9 /chrome/browser/process_singleton_linux.cc
parent7ec7c1899afc8537bb25ce373aa2e136aa7788dc (diff)
downloadchromium_src-fe63292b5ff8a734578877d192c7f89aa3845e87.zip
chromium_src-fe63292b5ff8a734578877d192c7f89aa3845e87.tar.gz
chromium_src-fe63292b5ff8a734578877d192c7f89aa3845e87.tar.bz2
Blacklist all the message port related layout tests for now. I couldn't figure out how to get chrome_dll to use a different PlatformMessagePortChannel implementation from test_shell (see http://codereview.chromium.org/160570 for what I tried). I gave up afterwards, since anyways they test that the default WebKit implementation works, which we know from the WebKit buildbot. Our multi-process implementation is tested using ui_tests.
Review URL: http://codereview.chromium.org/160574 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22363 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/process_singleton_linux.cc')
0 files changed, 0 insertions, 0 deletions