feature request: Order by step duration button for steps |
|||
Issue descriptionI'd like to see most time consuming step easily in the build page.
,
Mar 8 2018
,
Mar 8 2018
I'm not sure we want to make this a first class feature in the UI. Would you be able to use the dremel/bigquery table? I think this is a LUCI builder and the bigquery table isn't ready yet but will be soon.
,
Mar 8 2018
BQ steps for LUCI were just announced g/luci-announce/IVdte3E-FRw/56A9NhHzAwAJ i think this use case is a bit different. Here a user is interested in one build, at hand. FWIW the Poluci hack has it https://luci-ui.appspot.com/p/chromium/buckets/try/builders/linux_chromium_rel_ng/42527 see gray area inside step bars
,
Mar 8 2018
forgot to mention: I am not sure reordering is a good idea, though. I think "see most time consuming step easily" can be achieved in a different way.
,
Mar 8 2018
A timeline view has been a fairly popular solution in alternate views (eg ChromeOS's dashboards)
,
Mar 8 2018
BQ is possibly still good for this, e.g. someone can use: bq --project_id=cr-buildbucket-dev query --use_legacy_sql=false "SELECT s.name, TIMESTAMP_DIFF(s.end_time, s.start_time, MINUTE) mins FROM \`cr-buildbucket.builds.completed_BETA\`, UNNEST(steps) s WHERE builder.project='chromium' AND builder.bucket='try' AND builder.builder='linux_chromium_rel_ng' AND number=41441 ORDER BY mins DESC LIMIT 10" A wrapper script to parameterize builder and number would also be practical.
,
Mar 8 2018
#4 luci-ui is nice! The ui let me know which steps are dominant part in the build easily. Is it possible to have such feature in luci-milo also? #7 Yes, we can get steps ordered by duration by BQ. But if I could get the result by few clicks instead of copying builder and build number to BQ query, I will be happy.
,
Mar 12 2018
Hmm, if we just need the feature that's in luci-ui that might not be too bad since it doesn't require client-side logic. I think we can look at adding this later.
,
Mar 21 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by efoo@chromium.org
, Mar 8 2018