Chris Wren 52020492f2 don't pin ranking updates at the end of the queue.
Apparently we schedule ranking updates all the time, so the job gets pulled
to the end of the queue, and can get starved. This change makes sure we
don't schedule multiple updates by leaving it in the queue. If a job in the
queue behind hte update request needs to send an update it will jsut
request one anyway, so we shouldn't miss updates.

Bug: 28015158
Change-Id: Id5b9d05ea6eb35e610ee34651e4cde8cddd4ae66
2016-04-06 11:12:02 -04:00
2016-04-02 19:31:19 -06:00
2016-03-31 13:23:15 -07:00
2016-03-30 19:41:05 +00:00
2016-03-31 10:00:09 -04:00
2016-04-04 10:23:57 -07:00
2016-03-03 10:19:27 -08:00
Description
No description provided
5.1 GiB
Languages
Java 77.3%
Kotlin 9.2%
PowerBuilder 6.6%
C++ 5.5%
AIDL 1%