commit 16434c2b20b7fe0b498ada40c5f43180f5f21af0
author Olivier Gaillard <gaillard@google.com> Tue Feb 05 12:44:58 2019 +0000
committer Olivier Gaillard <gaillard@google.com> Wed Feb 06 12:49:07 2019 +0000
tree 35ba67a802f68a390da854d23a4973400ffbcbc0
parent b5958a1d59d4bdc1a03cfcc99c9c911c3eb352d9

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