Bug 262899 - (safe-)merge-queue should expose its status
Summary: (safe-)merge-queue should expose its status
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2023-10-09 10:27 PDT by Sam Sneddon [:gsnedders]
Modified: 2023-10-23 17:11 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Sneddon [:gsnedders] 2023-10-09 10:27:15 PDT
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.
Comment 1 Radar WebKit Bug Importer 2023-10-09 10:27:28 PDT
<rdar://problem/116687268>
Comment 2 Brianna Fan 2023-10-18 15:41:41 PDT
Pull request: https://github.com/WebKit/WebKit/pull/19254
Comment 3 EWS 2023-10-23 17:11:31 PDT
Committed 269684@main (9c1e3b2893b0): <https://commits.webkit.org/269684@main>

Reviewed commits have been landed. Closing PR #19254 and removing active labels.