| commit | 325768c9b2e936d3018240a1209bb8fb01b06d98 | [log] [tgz] |
|---|---|---|
| author | Christopher Tate <ctate@google.com> | Wed Mar 07 16:07:56 2018 -0800 |
| committer | Christopher Tate <ctate@google.com> | Thu Mar 08 18:38:11 2018 -0800 |
| tree | e4024c6430d8f9a66627f70d273801f88c65812d | |
| parent | 655d98bdb5787095f36a959566771b13c1966575 [diff] |
Track last job execution in heartbeat time, not strictly real time We need to be able to handle instrumented / externally driven job scheduling time, so we need to decouple that from "real" time. One other effect is getting a cross-call to the usage stats module out of the hot path of job runnability evaluation. Bug: 73664387 Bug: 70297229 Test: atest CtsJobSchedulerTestCases Change-Id: I0dce8af6e7fc50ce736b13572482b2db33e42b02