Issue metadata
Sign in to add a comment
|
Compress (or leave out) trigger steps from tryrun reports
Reported by
sigbjo...@opera.com,
May 25 2016
|
||||||||||||||||||||||||
Issue descriptionThe tryrun reports for some bots have a large (and increasing) number of [trigger] steps, e.g., https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_rel_ng/builds/235358 has ~90 of them. These seem to serve some internal diagnostic purpose only(?) and are of lesser interest to the blink/chromium developer inspecting status of a run. How about collapsing the trigger steps into one, or perhaps even leave them out?
,
May 28 2016
+swarming in case maruel has thoughts on this.
,
Aug 9 2016
This would be nice; I think that we could hide those under a nested step. Right now, nested steps aren't really supported well, though. One day we should do that, though.
,
May 15 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sigbjo...@opera.com
, May 25 2016