Steps to reproduce:
1) Go to any Milo results page - I was on https://luci-milo.appspot.com/buildbot/chromium.perf/Mac%20Pro%2010.11%20Perf/1369
2) Scroll down to a swarming task.
3) Look in the upper right hand corner of the task, there's a time duration: in the one I'm looking at (storage.indexxeddb_endure_tracing.reference on ATI GPU on Mac on Mac-10.11), I see "( 5 secs )".
EXPECTED: The number should show the task's duration.
ACTUAL: The task's duration is 4m23s (see duration.png), but the number in the upper right hand corner reads 5s (see collection_time.png).
The fact that the task duration isn't readily visible on this page has a significant impact on our perfbot health sheriffs: it turns the 30s process of identifying the long swarming tasks into at least a 20-30m process because there are 121 benchmarks (242 if you include their reference builds), each of which need to be visited in order to understand what's taking so long.
Comment 1 by charliea@chromium.org
, Aug 23 2017NextAction: 2017-08-25