build-dumprendertree and build-webkittestrunner should both build WebCore test support libraries.
<rdar://problem/48278600>
Created attachment 362640 [details] Patch
Patch doesn’t look right. Why only for Cocoa platforms? Why doing it after we build drt or wktr?
Why change directories?
Why is this useful? As these libraries are built together with WebCore, I expect them to always be present. I’m probably missing some context here.
(In reply to Daniel Bates from comment #3) > Patch doesn’t look right. Why only for Cocoa platforms? Why doing it after > we build drt or wktr? Read the whole file. Other platforms, to quote the existing comment, "# GTK+, WPE, PlayStation, and Windows build everything in one shot. No need to build anything here."
(In reply to Daniel Bates from comment #3) > Why only for Cocoa platforms? By comment 6. > Why doing it after we build drt or wktr? Still unanswered.
(In reply to Daniel Bates from comment #4) > Why change directories? Okay, read more of the existing code. Answer, that’s how it’s done. The build...() seems to assume you’re in the same directory as the Xcode project.
(In reply to Alexey Proskuryakov from comment #5) > Why is this useful? As these libraries are built together with WebCore, I > expect them to always be present. > > I’m probably missing some context here. Read radar.
Actually Alexy’s question adds to my feeling that this patch doesn’t look right because this problem is only hit for Apple engineers hence the radar description. So, this fix seems misplaced.
So, either something very similar to this patch is the fix, or this isn't a bug. We run build-webkittestrunner right before running tests, by default. We don't make an attempt to build the entire WebKit stack, we never have nor should we (A no-op build of WebKit through build-webkit actually takes ~30 seconds-1 minute). Apparently there is a workflow where WebCore can be built without building the WebCore test support libraries.
(In reply to Jonathan Bedard from comment #11) > So, either something very similar to this patch is the fix, or this isn't a > bug. > > We run build-webkittestrunner right before running tests, by default. We > don't make an attempt to build the entire WebKit stack, we never have nor > should we (A no-op build of WebKit through build-webkit actually takes ~30 > seconds-1 minute). > Apparently there is a workflow where WebCore can be built > without building the WebCore test support libraries. This is the bug! It’s an Apple Internal thing. Fix this!
This Bugzilla bug is invalid. The radar bug is valid.
Created attachment 362724 [details] Patch