Bug 205315 - test-lldb-webkit: Run in CI
Summary: test-lldb-webkit: Run in CI
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Jonathan Bedard
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-12-16 16:56 PST by Jonathan Bedard
Modified: 2019-12-18 16:35 PST (History)
6 users (show)

See Also:


Attachments
Patch (19.20 KB, patch)
2019-12-16 16:57 PST, Jonathan Bedard
no flags Details | Formatted Diff | Diff
Patch (20.11 KB, patch)
2019-12-16 17:54 PST, Jonathan Bedard
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Bedard 2019-12-16 16:56:13 PST
We should run test-lldb-webkit in our continuous integration.
Comment 1 Jonathan Bedard 2019-12-16 16:57:46 PST
Created attachment 385832 [details]
Patch
Comment 2 Alexey Proskuryakov 2019-12-16 17:04:29 PST
Comment on attachment 385832 [details]
Patch

I think that you also need to add the new step to the list of consequential steps that make the bot watcher’s bubble red. 

Not sure if we have enough code shared for this to run on EWS. Probably not.
Comment 3 Jonathan Bedard 2019-12-16 17:18:53 PST
(In reply to Alexey Proskuryakov from comment #2)
> Comment on attachment 385832 [details]
> Patch
> 
> I think that you also need to add the new step to the list of consequential
> steps that make the bot watcher’s bubble red. 
> 
> Not sure if we have enough code shared for this to run on EWS. Probably not.

I did look into EWS. It's a bit more complicated there and I'm not 100% sure the right architecture. It's a tools test, so it seems like it should run in the same way that test-webkitpy does, but it also requires a built binary, so it probably needs to run the same way API tests do. That will likely mean another bubble along with sharing machines with API tests (probably).

I was going to do that in a separate patch, and while I'd like to take a stab at it (because someone other than Aakash needs to understand EWS, and something like this is a great way for me to do that), I really wouldn't feel comfortable landing that change without an r+ from Aakash.
Comment 4 Jonathan Bedard 2019-12-16 17:54:22 PST
Created attachment 385841 [details]
Patch
Comment 5 Alexey Proskuryakov 2019-12-16 19:27:36 PST
Comment on attachment 385841 [details]
Patch

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

> Tools/BuildSlaveSupport/build.webkit.org-config/steps.py:652
> +    command = [

Reporting results to flakiness dashboard is another missing piece of course.
Comment 6 Jonathan Bedard 2019-12-16 22:30:42 PST
(In reply to Alexey Proskuryakov from comment #5)
> Comment on attachment 385841 [details]
> Patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=385841&action=review
> 
> > Tools/BuildSlaveSupport/build.webkit.org-config/steps.py:652
> > +    command = [
> 
> Reporting results to flakiness dashboard is another missing piece of course.

Yes, not difficult to add in later on, just not sure we actually want reporting here.
Comment 7 WebKit Commit Bot 2019-12-16 23:15:12 PST
Comment on attachment 385841 [details]
Patch

Clearing flags on attachment: 385841

Committed r253611: <https://trac.webkit.org/changeset/253611>
Comment 8 WebKit Commit Bot 2019-12-16 23:15:14 PST
All reviewed patches have been landed.  Closing bug.
Comment 9 Radar WebKit Bug Importer 2019-12-16 23:16:21 PST
<rdar://problem/57997959>
Comment 10 Jonathan Bedard 2019-12-18 16:35:26 PST
Committed r253729: <https://trac.webkit.org/changeset/253729>