RESOLVED FIXED 187357
[ews-build] Add build step to UnApply patch
https://bugs.webkit.org/show_bug.cgi?id=187357
Summary [ews-build] Add build step to UnApply patch
Aakash Jain
Reported 2018-07-05 12:41:50 PDT
When a patch fails to build or fails layout-tests, EWS should unapply the patch and build/test again. We should add the build step to unapply the patch.
Attachments
Proposed patch (1.77 KB, patch)
2018-07-05 13:38 PDT, Aakash Jain
ap: review+
ews-watchlist: commit-queue-
Archive of layout-test-results from ews204 for win-future (12.88 MB, application/zip)
2018-07-05 17:16 PDT, EWS Watchlist
no flags
Aakash Jain
Comment 1 2018-07-05 13:38:57 PDT
EWS Watchlist
Comment 2 2018-07-05 13:41:27 PDT Comment hidden (obsolete)
EWS Watchlist
Comment 3 2018-07-05 17:16:16 PDT Comment hidden (obsolete)
EWS Watchlist
Comment 4 2018-07-05 17:16:26 PDT Comment hidden (obsolete)
Aakash Jain
Comment 5 2018-07-10 16:43:27 PDT
Radar WebKit Bug Importer
Comment 6 2018-07-10 16:45:16 PDT
Daniel Bates
Comment 7 2018-07-16 15:41:17 PDT
Comment on attachment 344360 [details] Proposed patch View in context: https://bugs.webkit.org/attachment.cgi?id=344360&action=review > Tools/BuildSlaveSupport/ews-build/steps.py:73 > + super(UnApplyPatchIfRequired, self).__init__(alwaysUseLatest=True, **kwargs) From my understanding setting alwaysUseLatest to true both cleans the working directory and pulls down new source changes. This represents a behavior change from the current EWS. The current EWS actually unapplies the patch. It does this implicitly by cleaning the working directory. That is, it does not both clean the working directory and pull down new source changes.
Note You need to log in before you can comment on or make changes to this bug.