| Summary: | [ews-build] Hide build steps to compress, upload and unzip layout-test-results | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Aakash Jain <aakash_jain> | ||||
| Component: | Tools / Tests | Assignee: | Aakash Jain <aakash_jain> | ||||
| Status: | RESOLVED WORKSFORME | ||||||
| Severity: | Normal | CC: | aakash_jain, ap, jbedard | ||||
| Priority: | P2 | ||||||
| Version: | Other | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=200048 | ||||||
| Attachments: |
|
||||||
|
Description
Aakash Jain
2019-07-23 16:19:14 PDT
Created attachment 374729 [details]
Patch
Sample runs: https://ews-build.webkit-uat.org/#/builders/34/builds/57 https://ews-build.webkit-uat.org/#/builders/35/builds/153 I'm skeptical about this one. It's good to have the buildbot page as nice as possible, but we will never make it user friendly. So hiding things that are necessary for understanding and debugging EWS seems like over-shooting. I'd like to see an example of the old 'cluttered' look for comparison. I also don't see an obvious way to reveal hidden steps if we wanted to, am I missing something in the buildbot UI? (In reply to Jonathan Bedard from comment #4) > I'd like to see an example of the old 'cluttered' look for comparison. https://ews-build.webkit-uat.org/#/builders/34/builds/35 > I also don't see an obvious way to reveal hidden steps if we wanted to, am I missing something in the buildbot UI? Nope, you are right, there is no obvious way to reveal hidden step. For debugging you can get the info through API though. (In reply to Aakash Jain from comment #5) > (In reply to Jonathan Bedard from comment #4) > > I'd like to see an example of the old 'cluttered' look for comparison. > https://ews-build.webkit-uat.org/#/builders/34/builds/35 > > > I also don't see an obvious way to reveal hidden steps if we wanted to, am I missing something in the buildbot UI? > Nope, you are right, there is no obvious way to reveal hidden step. For > debugging you can get the info through API though. It's a shame we can't just collapse steps and make them visible on request. I don't think these steps actually provide any information, so I don't see a problem hiding then, even if there isn't a way to expose them in the UI. I don't see these steps ever being needed to understand and debug EWS, but perhaps there is an issue don't have in mind. > I don't think these steps actually provide any information Agree, that's what motivated me to write this patch. > , so I don't see a problem hiding then, even if there isn't a way to expose them in the UI. > I don't see these steps ever being needed to understand and debug EWS, but > perhaps there is an issue don't have in mind. Note that these step would be hidden only when they PASS, so any failures will be visible. One issue I can think of is slow (but still working) upload. The step would be visible while it's running, so if it's too slow we could notice it while it's running. > I don't think these steps actually provide any information Agree, that's what motivated me to write this patch. > , so I don't see a problem hiding then, even if there isn't a way to expose them in the UI. > I don't see these steps ever being needed to understand and debug EWS, but > perhaps there is an issue don't have in mind. Note that these step would be hidden only when they PASS, so any failures will be visible. One issue I can think of is slow (but still working) upload. The step would be visible while it's running, so if it's too slow we could notice it while it's running. (In reply to Alexey Proskuryakov from comment #3) > I'm skeptical about this one. It's good to have the buildbot page as nice as > possible, but we will never make it user friendly. So hiding things that are > necessary for understanding and debugging EWS seems like over-shooting. Yeah, this one is just to make the buildbot page nicer (hopefully without affecting our ability to debug any issues). We will still be developing another page in https://bugs.webkit.org/show_bug.cgi?id=197522 I guess we just disagree about whether hiding information on a page that's primarily meant for debugging is desirable. If this ever confuses anyone even for five minutes, then it doesn't seem worth it to me. (In reply to Alexey Proskuryakov from comment #10) > I guess we just disagree about whether hiding information on a page that's > primarily meant for debugging is desirable. If this ever confuses anyone > even for five minutes, then it doesn't seem worth it to me. ok, let's just skip this patch. The benefit isn't much, and we know atleast one scenario (slow upload) in which this can make it harder to debug issues. |