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

Commit 9fa0f3f3 authored by Kweku Adams's avatar Kweku Adams Committed by Automerger Merge Worker
Browse files

Merge "Remove wtf." into tm-dev am: 2998b5aa 

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/17943049



Change-Id: I7ac15ad1cbab0db3fbaadb203b4bbf299bb01c3d
Signed-off-by: default avatarAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
parents 2127177a 2998b5aa

apex/jobscheduler/service/java/com/android/server/job/JobSchedulerService.java

+7 −2
Original line number Diff line number Diff line
@@ -1749,8 +1749,13 @@ public class JobSchedulerService extends com.android.server.SystemService 
        if (!removed) {

            // We never create JobStatus objects for the express purpose of removing them, and this

            // method is only ever called for jobs that were saved in the JobStore at some point,

            // so if we can't find it, something went seriously wrong.

            Slog.wtfStack(TAG, "Job didn't exist in JobStore");

            // so if we can't find it, something may be wrong. As of Android T, there is a

            // legitimate code path where removed is false --- when an actively running job is

            // cancelled (eg. via JobScheduler.cancel() or the app scheduling a new job with the

            // same job ID), we remove it from the JobStore and tell the JobServiceContext to stop

            // running the job. Once the job stops running, we then call this method again.

            // TODO: rework code so we don't intentionally call this method twice for the same job

            Slog.w(TAG, "Job didn't exist in JobStore");

        }

        if (mReadyToRock) {

            for (int i = 0; i < mControllers.size(); i++) {