RESOLVED FIXED 222676
REGRESSION(r273814): Unresolved types in JavaScriptCore-4.0.gir 
https://bugs.webkit.org/show_bug.cgi?id=222676
Summary REGRESSION(r273814): Unresolved types in JavaScriptCore-4.0.gir
WebKit Commit Bot
Reported 2021-03-03 12:20:11 PST
https://trac.webkit.org/changeset/273814 broke the build: Unresolved types in JavaScriptCore-4.0.gir This is an automatic bug report generated by webkitbot. If this bug report was created because of a flaky test, please file a bug for the flaky test (if we don't already have one on file) and dup this bug against that bug so that we can track how often these flaky tests fail.
Attachments
REVERT of r273814 (26.01 KB, patch)
2021-03-03 12:20 PST, WebKit Commit Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2021-03-03 12:20:26 PST
Created attachment 422133 [details] REVERT of r273814 Any committer can land this patch automatically by marking it commit-queue+. The commit-queue will build and test the patch before landing to ensure that the revert will be successful. This process takes approximately 15 minutes. If you would like to land the revert faster, you can use the following command: webkit-patch land-attachment ATTACHMENT_ID where ATTACHMENT_ID is the ID of this attachment.
EWS
Comment 2 2021-03-03 13:07:22 PST
commit-queue failed to commit attachment 422133 [details] to WebKit repository. To retry, please set cq+ flag again.
EWS
Comment 3 2021-03-03 13:11:02 PST
commit-queue failed to commit attachment 422133 [details] to WebKit repository. To retry, please set cq+ flag again.
EWS
Comment 4 2021-03-03 13:14:29 PST
commit-queue failed to commit attachment 422133 [details] to WebKit repository. To retry, please set cq+ flag again.
EWS
Comment 5 2021-03-03 13:29:15 PST
Committed r273836: <https://commits.webkit.org/r273836> All reviewed patches have been landed. Closing bug and clearing flags on attachment 422133 [details].
Radar WebKit Bug Importer
Comment 6 2021-03-03 13:30:16 PST
<rdar://problem/75000770>
Note You need to log in before you can comment on or make changes to this bug.