Consolidate the fast/loader and fast/loading directories
Created attachment 99006 [details] Patch
Comment on attachment 99006 [details] Patch Attachment 99006 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/8948974 New failing tests: fast/loader/subframe-removes-itself.html
Created attachment 99011 [details] Archive of layout-test-results from ec2-cr-linux-01 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: ec2-cr-linux-01 Port: Chromium Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
Maybe I did not spot the changes needed for Chromium test expectations? Could someone with some Chromium expertise help me out with this?
> Could someone with some Chromium expertise help me out with this? Sure.
Comment on attachment 99006 [details] Patch I didn't see anything obvious, but I'll figure it out and land this patch for you.
The moved test would have failed on all platforms. The old directory apparently used to trigger an implicit call to dumpFrameLoadCallbacks. I've added an explicit call to preserve the intent of the test.
Created attachment 99040 [details] Patch for landing
Comment on attachment 99040 [details] Patch for landing Clearing flags on attachment: 99040 Committed r89994: <http://trac.webkit.org/changeset/89994>
All reviewed patches have been landed. Closing bug.
(In reply to comment #7) > The moved test would have failed on all platforms. Oh, got it. How could I have missed that?! Thanks very much for taking care of this.
My pleasure.