Bug 70266

Summary: [meta] Polish garden-o-matic's builder failure UI
Product: WebKit Reporter: Dimitri Glazkov (Google) <dglazkov>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: aakash_jain, ahmad.saleem792, ap, lingho
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 65228, 70259, 70261, 70262, 70279    
Bug Blocks: 69227    

Dimitri Glazkov (Google)
Reported 2011-10-17 13:33:03 PDT
Umbrella.
Attachments
Ahmad Saleem
Comment 1 2024-03-09 18:27:45 PST
@Alexey - I think this was from Chromium port (pre-Blink) infrastructure and not relevant for WebKit anymore. Should we close this bug and all dependent and blocker bugs (if all are about 'garden-o-matic'.
Alexey Proskuryakov
Comment 2 2024-03-11 09:14:26 PDT
I think that's it's probably gone, but not quite sure, I've never used this tool. We still have quite a few references to it in the repository, including a website page at Tools/CISupport/build-webkit-org/public_html/TestFailures/garden-o-matic.html. But I cannot access it at https://build.webkit.org/TestFailures/garden-o-matic.html Adding Ling and Aakash, who would know more about whether Tools/CISupport/build-webkit-org/public_html is supposed to show up on the actual website. Perhaps we need to delete all this code.
Ahmad Saleem
Comment 3 2024-03-11 09:15:20 PDT
(In reply to Alexey Proskuryakov from comment #2) > I think that's it's probably gone, but not quite sure, I've never used this > tool. We still have quite a few references to it in the repository, > including a website page at > Tools/CISupport/build-webkit-org/public_html/TestFailures/garden-o-matic. > html. But I cannot access it at > https://build.webkit.org/TestFailures/garden-o-matic.html > > Adding Ling and Aakash, who would know more about whether > Tools/CISupport/build-webkit-org/public_html is supposed to show up on the > actual website. Perhaps we need to delete all this code. I asked Aakash on Slack as well last week. :-)
Note You need to log in before you can comment on or make changes to this bug.