Bug 28397 - [Chromium] Upstream Chromium port test baselines
Summary: [Chromium] Upstream Chromium port test baselines
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Dirk Pranke
URL:
Keywords:
: 36330 (view as bug list)
Depends on:
Blocks: 28395 28398
  Show dependency tree / graph
 
Reported: 2009-08-17 10:33 PDT by Dimitri Glazkov (Google)
Modified: 2010-03-22 09:29 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitri Glazkov (Google) 2009-08-17 10:33:34 PDT 
If we want to run layout tests out of svn.webkit.org, we should have our baselines (and expectations) live upstream. This is a master bug to track the progress on this effort.
Comment 1 Dimitri Glazkov (Google) 2009-08-17 12:32:55 PDT 
This probably shouldn't be tackled head-on: there are currently 24177 files weighing about 260MB in http://src.chromium.org/viewvc/chrome/trunk/src/webkit/data/layout_tests/platform/

I don't think adding these to LayoutTests/platform/ is prudent.

Perhaps they could be an external dependency?
Comment 2 Ojan Vafai 2009-08-17 13:06:44 PDT 
Wouldn't having them as an external dependency mean that people would need to check out chromium code in order to change a test's baseline for chromium?
Comment 3 Dimitri Glazkov (Google) 2009-08-17 13:45:55 PDT 
(In reply to comment #2)
> Wouldn't having them as an external dependency mean that people would need to
> check out chromium code in order to change a test's baseline for chromium?

You're right. With other ports starting to steadily check in their test expectations as well, how will we handle this?
Comment 4 Pam Greene (IRC:pamg) 2009-08-19 12:27:29 PDT 
I currently check out all the platform results for Mac, QT, etc., even though I don't use them. Granted that the platform/chromium results are much larger, it still seems better to me to include them in the repository like any other port. The first update afterward is painful, but the ongoing cost of ~250 MB isn't that bad.

I'd probably support a more general solution to letting people pick which parts of the repository they wanted to check out... but Ojan has a good point about baselines.
Comment 5 Dimitri Glazkov (Google) 2010-03-02 07:51:50 PST 
We're uploading these straight-up.
Comment 6 Dirk Pranke 2010-03-18 15:41:47 PDT 
*** Bug 36330 has been marked as a duplicate of this bug. ***