IssueTracker

Consider following scenario (everything for the same workSpecId) :

1. StartWorkRunnable was posted as a result of GreedyScheduler
2. WorkerWrapper was created by Processor
3. StopWorkRunnable posted by GreedyScheduler because constraints aren't met anymore or (in the future because of an update of workspec)
4. onStartJob is called on main thread => new params added to mJobParameters and StartWorkRunnable was posted.
5. onExecuted in SystemJobService was called due to 3. on the main thread => SystemJobService removes corresponding entry from mJobParameters and calls jobFinished signalling JobScheduler that job finished running => JobScheduler stops constraints tracking.
6. Worker is started again because of 4, but neither GreedyScheduler or JobScheduler track constraints.