diff options
author | Olivier Gaillard <gaillard@google.com> | 2019-02-06 13:18:09 +0000 |
---|---|---|
committer | Olivier Gaillard <gaillard@google.com> | 2019-02-08 11:43:40 +0000 |
commit | 11203df2a2e774c62297c76202253a3ccf154cc3 (patch) | |
tree | 725afb865d9741b39e001bcbc30c836d30078323 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
parent | f0cdc78790c4eecea498be370667d247e16e3ee1 (diff) |
Unify the way we process events on condition change and bucket
boundaries.
- We now always process empty data and events that exceeds the max delay
in a consistent way
- Fix one bug which caused base data not to be reset, e.g.
bucket h+1 on condition change to true, we pull the following data (key A / value 1, key B / value 2)
bucket h+2 on bucket boundary, we pull the following data (key A / value 2)
In this case the previous code, did not reset Key B. It should be reset
since it is not present in the most recent data.
Test: atest statsd_test
Bug: 124046337
Change-Id: I19456bbe1529e72befbb621be185ce24bd65077a
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions