| commit | c59d3ef43334e7a242097cfd626dc79816727ad1 | [log] [tgz] |
|---|---|---|
| author | Derek Gonyeo <dgonyeo@google.com> | Tue Dec 18 14:56:09 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Dec 19 00:16:01 2018 +0000 |
| tree | 0ef0f76231797b2873e8441a0e197019e68b90f1 | |
| parent | a2e5a3a16b70d217472168c183e9c670ddf50938 [diff] |
[log_listener] fix logic bug with 0-sized MaxCapacityFiles A recent change to support MaxCapacityFiles with a max capacity of 0 bytes wasn't implemented correctly, and on writes claimed no bytes were written to the always-empty file. Now, it will claim all bytes were successfully written, as all bytes will always be correctly handled (i.e. discarded) in this case. TEST: added unit test to cover this case Change-Id: I734422257430bb7e527ea47068ebaa36fb285892