Bug 209060

Summary: [ews] run FindModifiedChangeLogs early in the build
Product: WebKit Reporter: Aakash Jain <aakash_jain>
Component: Tools / TestsAssignee: Aakash Jain <aakash_jain>
Status: RESOLVED FIXED    
Severity: Normal CC: aakash_jain, ap, commit-queue, jbedard, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Aakash Jain
Reported 2020-03-13 10:24:32 PDT
[ews] run FindModifiedChangeLogs build-step early in the build. This would reduce the duration between updating to ToT and committing the patch.
Attachments
Patch (2.83 KB, patch)
2020-03-13 10:27 PDT, Aakash Jain 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Aakash Jain
Comment 1 2020-03-13 10:27:17 PDT
Created attachment 393498 [details] Patch
Jonathan Bedard
Comment 2 2020-03-13 11:51:30 PDT
Comment on attachment 393498 [details] Patch Does it make sense to do this before compiling and testing? Or should we do it after compiling and testing, but before updating?
Aakash Jain
Comment 3 2020-03-13 11:59:21 PDT
(In reply to Jonathan Bedard from comment #2) > Does it make sense to do this before compiling and testing? Or should we do it after compiling and testing, but before updating? Probably doesn't make much difference. Might be slightly better before compiling, just after applying the patch (since git status would be based on only patch contents).
WebKit Commit Bot
Comment 4 2020-03-13 12:33:43 PDT
Comment on attachment 393498 [details] Patch Clearing flags on attachment: 393498 Committed r258420: <https://trac.webkit.org/changeset/258420>
WebKit Commit Bot
Comment 5 2020-03-13 12:33:45 PDT
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 6 2020-03-13 12:34:16 PDT
<rdar://problem/60428905>
Aakash Jain
Comment 7 2020-03-15 11:05:46 PDT
This change should reduce the chances of issues like https://bugs.webkit.org/show_bug.cgi?id=209125 (where landing failed, because during the time repo was updated to ToT and patch was attempted to be landed, there was another commit which modified similar files).
Note You need to log in before you can comment on or make changes to this bug.