The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/63fe748ccc5eacb4450dc43bc9e957662dabaefb

commit 63fe748ccc5eacb4450dc43bc9e957662dabaefb
Author: Sean McCullough <seanmccullough@chromium.org>
Date: Mon Apr 02 22:41:47 2018

[test-results] Store the test run times.

Bug:  828092 
Change-Id: I55a1377203dcdf03fd9497489b294c46e10cc027
Reviewed-on: https://chromium-review.googlesource.com/991092
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Sean McCullough <seanmccullough@chromium.org>

[modify] https://crrev.com/63fe748ccc5eacb4450dc43bc9e957662dabaefb/go/src/infra/appengine/test-results/frontend/event_logging.go
[modify] https://crrev.com/63fe748ccc5eacb4450dc43bc9e957662dabaefb/go/src/infra/appengine/test-results/model/full_result.go

This change is live on prod.  I pushed this to staging earlier and started to see timing getting populated there. On prod I still don't see any run times for that particular step, but that may be because it hasn't run again since the test-results server update.

See if this query returns anything after the next time it runs:

SELECT max(start_time), max(run.time), max(run.times), count(*) FROM [test-results-hrd:events.test_results] WHERE buildbot_info.builder_name = "One Buildbot Step Test Builder"