| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This pull request modifies the Gradle build configuration to establish a dependency between the app's APK listing task and the benchmark packaging tasks, while also setting the default benchmark rules to BaselineProfile. The review identifies an inefficiency in the task configuration logic that could impact build performance and highlights a potential issue where the global benchmark rule setting might restrict other benchmarks in the module.
Sorry, something went wrong.
… scope enabledRules to nonMinifiedRelease build type
…ks variant resolution
|
Looks solid to me. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #1965
Problem
Two build errors occur when running generateProdReleaseBaselineProfile:
Error 1 — Instrumentation runner not found:
benchmarks/build.gradle.kts was missing testInstrumentationRunnerArguments with enabledRules=BaselineProfile. Without this, the managed device test runner executed macrobenchmarks alongside baseline profile generators, putting the app in an incorrect state and causing all profile generators to fail with NullPointerException and AssertionError.
Error 2 — Gradle 9 implicit task dependency:
Gradle 9 strict validation detected that :app:createProdNonMinifiedReleaseApkListingFileRedirect consumed output from :benchmarks:packageProdNonMinifiedRelease without declaring an explicit dependency, causing non-deterministic build failures.
Fix
Testing