BattOr agent should require more time elapse after stopping tracing and after a clock sync |
||
Issue descriptionRight now, we require that the trace run for 50ms after a clock sync. alexandermont@ is seeing instances where this isn't enough, so we should increase the amount to 150ms.
,
Mar 18 2016
Actually, Alex just tested it with 100ms and that seems to work fine, so we'll go with that.
,
Mar 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/54e1ece8abfcf5f93f05ba64e06c89f3b1f50d6c commit 54e1ece8abfcf5f93f05ba64e06c89f3b1f50d6c Author: charliea <charliea@chromium.org> Date: Mon Mar 21 14:35:34 2016 battor agent: Increases required time after clock sync to 100ms Sometimes the 50ms that was currently allotted wasn't enough for the sample that the clock sync marker took place at to make it into the trace. BUG= 596187 Review URL: https://codereview.chromium.org/1815383002 Cr-Commit-Position: refs/heads/master@{#382281} [modify] https://crrev.com/54e1ece8abfcf5f93f05ba64e06c89f3b1f50d6c/tools/battor_agent/battor_agent.cc
,
Mar 22 2016
Marking this as fixed. Please let me know if you see this problem crop up again. |
||
►
Sign in to add a comment |
||
Comment 1 by charliea@chromium.org
, Mar 18 2016