Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 83baaa12 authored by Chenjie Yu's avatar Chenjie Yu
Browse files

Fix pulling interval may become 0 in cts 

If the bucket size is lower than 1 min, the interval should be at least
1 min.

Bug: 74533948
Test: cts
Change-Id: Icb72579367cd12d3f475c7e2935b98c0ebc66419
parent c5d0ed9f

cmds/statsd/src/external/StatsPullerManagerImpl.cpp

+5 −0
Original line number Diff line number Diff line
@@ -166,6 +166,11 @@ void StatsPullerManagerImpl::RegisterReceiver(int tagId, wp<PullDataReceiver> re 
    // Round it to the nearest minutes. This is the limit of alarm manager.

    // In practice, we should limit it higher.

    long roundedIntervalMs = intervalMs/1000/60 * 1000 * 60;

    // Scheduled pulling should be at least 1 min apart.

    // This can be lower in cts tests, in which case we round it to 1 min.

    if (roundedIntervalMs < 60 * 1000) {

        roundedIntervalMs = 60 * 1000;

    }

    // There is only one alarm for all pulled events. So only set it to the smallest denom.

    if (roundedIntervalMs < mCurrentPullingInterval) {

        VLOG("Updating pulling interval %ld", intervalMs);