-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android 34 WorkManager Scheduler #6221
base: main
Are you sure you want to change the base?
Conversation
Release note changesNo release note changes were detected. If you made changes that should be |
Coverage Report 1Affected Products
Test Logs |
Size Report 1Affected Products
Test Logs |
Startup Time Report 1Note: Layout is sometimes suboptimal due to limited formatting support on GitHub. Please check this report on GCS. Startup time comparison between the CI merge commit (611ef21) and the base commit (adab25c) are not available. No macrobenchmark data found for the base commit (adab25c). Analysis for the CI merge commit (611ef21) can be found at: |
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Outdated
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Outdated
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Outdated
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Outdated
Show resolved
Hide resolved
...oogle/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerSchedulerWorker.java
Outdated
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Outdated
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Outdated
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Outdated
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Show resolved
Hide resolved
.../com/google/android/datatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java
Outdated
Show resolved
Hide resolved
int jobId = WorkScheduler.getJobId(context, transportContext); | ||
if (!force) { | ||
try { | ||
for (WorkInfo info : manager.getWorkInfosByTag("transport-" + jobId).get()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
getWorkInfosByTag
returns a list, but it should always be exactly 1, right? If that's the case, we need to verify that condition, as if it's not true something else has gone wrong, instead of looping through it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure, maybe it keeps finished jobs for some period of time? It wouldn't be a condition we verify though, scheduling can be called with force = true
beforehand and schedule multiple before calling with force = false
, I think.
…atatransport/runtime/scheduling/jobscheduling/WorkManagerScheduler.java Co-authored-by: Rodrigo Lazo <rlazo@users.noreply.github.com>
No description provided.