Bug 182580 - Gigacage DumpRenderTree and WebKitTestRunner
Summary: Gigacage DumpRenderTree and WebKitTestRunner
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: bmalloc (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on: 182457
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-07 13:43 PST by JF Bastien
Modified: 2020-01-24 09:18 PST (History)
11 users (show)

See Also:


Attachments
patch (2.97 KB, patch)
2018-02-07 13:46 PST, JF Bastien
ap: review-
ap: commit-queue-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description JF Bastien 2018-02-07 13:43:23 PST
As Saam suggested in #182457, this will give us better test coverage.
Comment 1 Radar WebKit Bug Importer 2018-02-07 13:45:06 PST
<rdar://problem/37325535>
Comment 2 JF Bastien 2018-02-07 13:46:27 PST
Created attachment 333310 [details]
patch
Comment 3 EWS Watchlist 2018-02-07 13:47:49 PST
Attachment 333310 [details] did not pass style-queue:


ERROR: Source/bmalloc/bmalloc/ProcessCheck.mm:38:  Extra space between ^ and block definition.  [whitespace/brackets] [4]
Total errors found: 1 in 2 files


If any of these errors are false positives, please file a bug against check-webkit-style.
Comment 4 Saam Barati 2018-02-07 15:06:18 PST
Comment on attachment 333310 [details]
patch

View in context: https://bugs.webkit.org/attachment.cgi?id=333310&action=review

> Source/bmalloc/bmalloc/ProcessCheck.mm:53
> +            || [processName hasPrefix:@"WebKitTestRunner"];

I don't think this is exactly what we should do. I think the goal should be for the testing environment to be a lot like the environment it's enabled in (e.g, when running the browser). Therefore, this should probably only be enabled in the
"WebKitTestRunner WebContent" process.
Comment 5 JF Bastien 2018-02-07 15:21:00 PST
(In reply to Saam Barati from comment #4)
> Comment on attachment 333310 [details]
> patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=333310&action=review
> 
> > Source/bmalloc/bmalloc/ProcessCheck.mm:53
> > +            || [processName hasPrefix:@"WebKitTestRunner"];
> 
> I don't think this is exactly what we should do. I think the goal should be
> for the testing environment to be a lot like the environment it's enabled in
> (e.g, when running the browser). Therefore, this should probably only be
> enabled in the
> "WebKitTestRunner WebContent" process.

Where does this name come from? Grepping around find a script that deals with "WebKitTestRunner Web Content" (note the space), but I can't find how we create it.
Comment 6 Saam Barati 2018-02-07 15:25:24 PST
(In reply to JF Bastien from comment #5)
> (In reply to Saam Barati from comment #4)
> > Comment on attachment 333310 [details]
> > patch
> > 
> > View in context:
> > https://bugs.webkit.org/attachment.cgi?id=333310&action=review
> > 
> > > Source/bmalloc/bmalloc/ProcessCheck.mm:53
> > > +            || [processName hasPrefix:@"WebKitTestRunner"];
> > 
> > I don't think this is exactly what we should do. I think the goal should be
> > for the testing environment to be a lot like the environment it's enabled in
> > (e.g, when running the browser). Therefore, this should probably only be
> > enabled in the
> > "WebKitTestRunner WebContent" process.
> 
> Where does this name come from? Grepping around find a script that deals
> with "WebKitTestRunner Web Content" (note the space), but I can't find how
> we create it.

No idea where it comes from.
Comment 7 Alexey Proskuryakov 2018-02-07 20:55:25 PST
That’s not the process name, it is only the name that LaunchServices uses for display purposes. The process name remains com.apple.webkit.WebContent.

I think that special casing the name is the wrong approach anyway. This should be an explicit opt-in that the client can elect to enable.
Comment 8 JF Bastien 2018-02-07 20:58:16 PST
(In reply to Alexey Proskuryakov from comment #7)
> That’s not the process name, it is only the name that LaunchServices uses
> for display purposes. The process name remains com.apple.webkit.WebContent.
> 
> I think that special casing the name is the wrong approach anyway.

For this specific change (DUmpRenderTree and WebKitTestRunner), or in general? A follow-up will make this an entitlement instead, but for now this general approach was decided to be the right approach.

> This should be an explicit opt-in that the client can elect to enable.
Comment 9 Alexey Proskuryakov 2018-02-07 23:20:34 PST
I don't know what the arguments were originally, but the fact that you now ran into difficulties demonstrates that it may have not been the right decision.