Add a benchmark to track BattOr clock sync latency |
||||||
Issue descriptionNed suggested this a while ago, and I think it's a great idea: in the interest of preventing regression in clock sync latency, we should create a Telemetry test that measures what the clock sync latency is for BattOrs. rnephew@, would you be willing to take this on?
,
Jun 20 2016
,
Jun 23 2016
,
Jun 23 2016
,
Jun 23 2016
,
Jun 24 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5cd4599fb20c05ab9063b03ef48caa69c3c453bc commit 5cd4599fb20c05ab9063b03ef48caa69c3c453bc Author: catapult-deps-roller <catapult-deps-roller@chromium.org> Date: Fri Jun 24 01:11:07 2016 Roll src/third_party/catapult/ 4aaa445b7..050a11fc5 (2 commits). https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/4aaa445b7b1a..050a11fc5569 $ git log 4aaa445b7..050a11fc5 --date=short --no-merges --format='%ad %ae %s' BUG= 618387 TBR=catapult-sheriff@chromium.org Review-Url: https://codereview.chromium.org/2095803002 Cr-Commit-Position: refs/heads/master@{#401768} [modify] https://crrev.com/5cd4599fb20c05ab9063b03ef48caa69c3c453bc/DEPS
,
Jul 14 2016
Marking this as fixed: the metric is now live. https://chromeperf.appspot.com/report?sid=9fcc9da6f30a4c3369709d31591c94631ea275a2cf5765512ed25bc742a43967 |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rnep...@chromium.org
, Jun 20 2016