Bug 225411

Summary: EWS bubbles should show current status after pressing 'Retry failed builds' button
Product: WebKit Reporter: Devin Rousso <hi>
Component: New BugsAssignee: Aakash Jain <aakash_jain>
Status: RESOLVED FIXED    
Severity: Normal CC: aakash_jain, ap, hi, jbedard, ryanhaddad, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
[fast-cq] Patch none

Devin Rousso
Reported 2021-05-05 13:23:28 PDT
IMO accessing "what is it doing now" is more important/useful than "what did it do before". Right now I don't know whether a "retry failures" patch is successfully/correctly in the bot's queue or if the bot is stuck or some other thing.
Attachments
Patch (1.60 KB, patch)
2021-05-05 16:40 PDT, Aakash Jain 		no flags
DetailsFormatted DiffDiff
[fast-cq] Patch (1.85 KB, patch)
2021-05-05 17:25 PDT, Aakash Jain 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Aakash Jain
Comment 1 2021-05-05 16:40:41 PDT
Created attachment 427817 [details] Patch
Aakash Jain
Comment 2 2021-05-05 17:24:10 PDT
To clarify the request here, even after clicking 'Retry failed builds' button, for the queue which were retried, the status-bubble keep linking to old builds (and keep showing old build info in hover-over message). This becomes confusing to some users, especially when the new build isn't started soon. A better way would be to not show old build info anymore, and link to the queue (in which the retry request is queued) instead of linking to old build.
Aakash Jain
Comment 3 2021-05-05 17:25:08 PDT
Created attachment 427830 [details] [fast-cq] Patch
EWS
Comment 4 2021-05-06 11:34:21 PDT
Committed r277103 (237405@main): <https://commits.webkit.org/237405@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 427830 [details].
Radar WebKit Bug Importer
Comment 5 2021-05-06 11:35:16 PDT
<rdar://problem/77617611>
Aakash Jain
Comment 6 2021-05-06 11:43:21 PDT
Deployed this change on the server.
Note You need to log in before you can comment on or make changes to this bug.