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

Commit b5194424 authored by Chenjie Yu's avatar Chenjie Yu Committed by android-build-merger
Browse files

Merge "Fix pulling interval may become 0 in cts" into pi-dev

am: 0421c2cf

Change-Id: Ib4b41d6b61df8f8e656d80345e76613b4aa03746
parents 528125af 0421c2cf
Loading
Loading
Loading
Loading
+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);