Status Update
No update yet.
Comments
ra...@google.com
Thanks for the report and all the details. Are you only seeing these build speed issues on CI? What's the build speed like in local development?
It would be great if you could share the compiler dump file with
sa...@gmail.com
Are you only seeing these build speed issues on CI? What's the build speed like in local development?
Hi, we usually don't run minified builds on our local environments, mainly because of the time it takes to run it and the amount of ram it would require.
I don't want to complain even more about it, but I'm sure you are already aware of the constraints that Android has. We already have the IDE taking +10GB, the Kotlin Compiler daemon (1-6GB depending on the compilation work needed), the Gradle daemon (usually around 14G at the end of the build). If we were to enable R8 on local builds, this would render local machines (even our beefy M1s) unable to use for minimum 15 minutes each time we would want to run the app. Devs will turn this off immediately.
A good starting point would be to check if there are any passes that take up an unusual amount of time.
Do you mean running the compiledump.py? Is this what the dump will be used for? If so, can I do that locally without any external tool? I'd rather not share the dump if I can test it myself. If there is more to it, then I'll try to upload it somewhere safe.
Description
Version used: 1.0.0
OS Version : pie (9.0)
Devices/Android versions reproduced on: HUAWEI BKL-L09
//snippet
val constraints = Constraints
.Builder()
.setRequiredNetworkType(NetworkType.CONNECTED)
.build()
//setUpdateCurrent - needed to schedule latest
val offlinePunchWorkRequest = OneTimeWorkRequest
.Builder(SavePunchWorker::class.java)
.setBackoffCriteria(BackoffPolicy.EXPONENTIAL, 1, TimeUnit.MINUTES)
.setConstraints(constraints)
.setInputData(createInputData(currentDateData))
.addTag("offlinePunch")
.build()
WorkManager
.getInstance()
.beginUniqueWork(currentDateData, ExistingWorkPolicy.APPEND, offlinePunchWorkRequest)
.enqueue()
finish()
I have scheduled the work request when network is not available,
after killing the application when network comes Job getting scheduled and getting this error in the Logcat
2019-03-08 13:10:03.945 1270-1270/? D/JobScheduler: Error executing JobStatus{cad0ba0 #u0a333/2
2019-03-08 13:10:21.945 1270-1270/? W/JobServiceContext: Time-out while trying to bind cad0ba0 #u0a333/2