Age jobs into runnability even in infrequent buckets
Actually use the "base heartbeats" of jobs when deciding runnability, so that now we properly sweep up all of the patiently-waiting jobs for a given bucket even if we can't quite get to them all within one heartbeat duration. Previously we would accidentally stop handling them until that bucket's next evaluation point, which might be far in the future. Now we're fair: once the app has waited an appropriate time, we can "catch up" all of its pending jobs, not just the ones we happen to fit into a relatively short period of time. Bug: 63527785 Test: manual Change-Id: I6b49b1f151df53bda59a64ead0c6c2a834a0dfe9
Loading
Please register or sign in to comment