Bug 248038
| Summary: | Contributors.json Optimization for EWS Checks | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ahmad Saleem <ahmad.saleem792> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | aakash_jain, jbedard, ryanhaddad |
| Priority: | P2 | ||
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 248037 | ||
Ahmad Saleem
Hi Team,
Based on Webkit Contributor discussion, I wanted to list down concerns about any Contributors.json file and what (in ideal world - which be might wrong) could help:
1) No need to raise bug - Document some place with updated instruction that don't create but on "bugs.webkit.org" - Less bugs to manage and better
2) No need to run whole EWS test suite - only run where it might matter - create small check once added, if any bug fails then the notification is being sent or not and all integration tests for this is working.
3) EWS build checks of compiling from tip and other is just resource usage and those can better utilised for other patches.
___
These are just pros and cons, I am aware as Contributor (from outside) and I am not totally familiar but I think it is still something better to evaluate and see, if we can do something.
Thanks!
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jonathan Bedard
Duping this to https://bugs.webkit.org/show_bug.cgi?id=248039, because I think they're really the same problem. Changes to `metadata` needs tools tests, but nothing else.
Jonathan Bedard
*** This bug has been marked as a duplicate of bug 248039 ***