Bug 251222
| Summary: | [ews] Run ValidateChange just before CompileWebKit and major steps | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Aakash Jain <aakash_jain> |
| Component: | Tools / Tests | Assignee: | Aakash Jain <aakash_jain> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Aakash Jain
EWS builds should run ValidateChange just after completing all the checkout operations.
This becomes more important because of skip-ews support. When using git-webkit pr --no-ews, skip-ews label is added by our tooling slightly after the PR creation. It races with build starting on bots, and builds can start (and pass the ValidateChange step which happens in the beginning of the build) before skip-ews label was added by the tooling. Since git operations like CleanGitRepo, CheckOutSource, CheckOutPullRequest takes few minutes, we should do the validation after those steps as well.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/104710968>
Aakash Jain
Pull request: https://github.com/WebKit/WebKit/pull/9187
Aakash Jain
Discussed with Jonathan. We also want to be conscious of number of api calls we make to GitHub as we might hit the api limit.
Changed it to run ValidateChange just before CompileWebKit and major steps.
EWS
Committed 259493@main (3808d4657839): <https://commits.webkit.org/259493@main>
Reviewed commits have been landed. Closing PR #9187 and removing active labels.