diff options
| author | Olivier Gaillard <gaillard@google.com> | 2019-02-05 12:44:58 +0000 |
|---|---|---|
| committer | Olivier Gaillard <gaillard@google.com> | 2019-02-06 12:49:07 +0000 |
| commit | c5f11c40064e4ba3a3aa66d58e466ae54005c4ac (patch) | |
| tree | c7875ef2ecc35e72c7cee97fc67794dfd7b686dc /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | af41d5f7bde649305d20b7d179755acb916ed3ce (diff) | |
Reset the base when pull fails.
Without resetting the base, we will compute the wrong diff when we have
a condition change.
Move the responsability of handling failures to the PullReceivers. This
is more consistent with #onConditionChanged which does handle the
failure cases.
We also always compute nextPullTimeNs in order to only call onDataPulled
on bucket boundaries. The current code does not update nextPullTimeNs
which means a new alarm might trigger a pull and onDataPulled in the
middle of the bucket. The behavior in this case is undefined.
Bug: 123181864
Test: atest statsd_test
Change-Id: I0910b7db26a0de764436c46c8d7d11cafa52dcd9
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions