RESOLVED FIXED 48836
[Chromium] Disable incremental linking for webkit_unit_test and DumpRenderTRee on x86 Windows on chromium build. 
https://bugs.webkit.org/show_bug.cgi?id=48836
Summary [Chromium] Disable incremental linking for webkit_unit_test and DumpRenderTRe...
Marc-Antoine Ruel
Reported 2010-11-02 08:05:50 PDT
Disable incremental linking for webkit_unit_test and DumpRenderTRee on x86 Windows on chromium build. It fails to link otherwise due to lack of virtual address space.
Attachments
Patch (2.36 KB, patch)
2010-11-02 08:09 PDT, Marc-Antoine Ruel 		no flags
DetailsFormatted DiffDiff
Patch (2.36 KB, patch)
2010-11-02 08:10 PDT, Marc-Antoine Ruel 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Marc-Antoine Ruel
Comment 1 2010-11-02 08:09:07 PDT
Created attachment 72667 [details] Patch
Marc-Antoine Ruel
Comment 2 2010-11-02 08:10:50 PDT
Created attachment 72668 [details] Patch
Marc-Antoine Ruel
Comment 3 2010-11-02 08:12:47 PDT
Please set c+. Tests now link on Windows XP slave: http://build.chromium.org/p/tryserver.chromium/builders/win_layout/builds/57
Marc-Antoine Ruel
Comment 4 2010-11-02 08:14:01 PDT
Please set c+. Tests now link on Windows XP slave: http://build.chromium.org/p/tryserver.chromium/builders/win_layout/builds/57
WebKit Commit Bot
Comment 5 2010-11-02 15:05:21 PDT
The commit-queue encountered the following flaky tests while processing attachment 72668 [details]: transitions/transition-end-event-transform.html http/tests/appcache/foreign-fallback.html Please file bugs against the tests. These tests were authored by ap@webkit.org, dino@apple.com, ojan@chromium.org, and pol@apple.com. The commit-queue is continuing to process your patch.
WebKit Commit Bot
Comment 6 2010-11-02 15:35:57 PDT
Comment on attachment 72668 [details] Patch Clearing flags on attachment: 72668 Committed r71179: <http://trac.webkit.org/changeset/71179>
WebKit Commit Bot
Comment 7 2010-11-02 15:36:02 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.