Change ui_tests to pull the directories it needs from the upstream webkit

Change ui_tests to pull the directories it needs from the upstream webkit
tree directly rather than relying on webkit/data/layout_tests for the
baselines. This requires us to change a few spots in the source code
because the directory naming conventions for platform-specific baselines
is different upstream (it's platform/chromium-win/foo rather than
platform/chromium-win/LayoutTests/foo).

Once this test lands we can (in theory) remove the downstream layout test baselines.

    BUG=none
    TEST=none
    R=dimich@chromium.org

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=43557

[Dmitry Titov, 2010-04-01 21:40:04]

http://codereview.chromium.org/1547009/diff/1/4
File chrome/test/ui/ui_layout_test.cc (right):

http://codereview.chromium.org/1547009/diff/1/4#newcode44
chrome/test/ui/ui_layout_test.cc:44: void
UILayoutTest::InitializeForLayoutTest(const FilePath& test_parent_dir,
this method is called in multiple places, prepending test_parent_dir with
"LayoutTests". I counted 7 call sites. Only 1 is updated not to include
"LayoutTest" (for RunWorkerFastLayoutTest)

[Dirk Pranke, 2010-04-01 22:51:16]

On 2010/04/01 21:40:04, Dmitry Titov wrote:
> http://codereview.chromium.org/1547009/diff/1/4
> File chrome/test/ui/ui_layout_test.cc (right):
> 
> http://codereview.chromium.org/1547009/diff/1/4#newcode44
> chrome/test/ui/ui_layout_test.cc:44: void
> UILayoutTest::InitializeForLayoutTest(const FilePath& test_parent_dir,
> this method is called in multiple places, prepending test_parent_dir with
> "LayoutTests". I counted 7 call sites. Only 1 is updated not to include
> "LayoutTest" (for RunWorkerFastLayoutTest)

Fixed (I think I found all of the right places). I also pulled in a couple of
missing chromium-win baseline dirs that were causing flaky tests to fail
consistently.

[Dmitry Titov, 2010-04-01 23:34:06]

LGTM

One thing - I see there is also chromium-mac/http/tests/workers upstream with a
single expectations file. If it's a dupe, lets file a bug in webkit to remove
it.