Bug 262899
| Summary: | (safe-)merge-queue should expose its status | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sam Sneddon [:gsnedders] <gsnedders> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bfan2, jbedard, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Sam Sneddon [:gsnedders]
https://github.com/WebKit/WebKit/pull/18834 had the "safe-merge-queue" label applied, and EWS fully succeeded at 16:18. I would perhaps naïvely expect it to have been merged by 17:00, given I'd expect it to be as quick as "unsafe-merge-queue" once EWS passes. But apparently it is at least as slow as "merge-queue" once EWS passes.
Fundamentally, the problem here is it is entirely opaque where in the merge-queue process anything is. We should have something (a comment? a status check?) that makes merge-queue progress observable.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/116687268>
Brianna Fan
Pull request: https://github.com/WebKit/WebKit/pull/19254
EWS
Committed 269684@main (9c1e3b2893b0): <https://commits.webkit.org/269684@main>
Reviewed commits have been landed. Closing PR #19254 and removing active labels.