commit | a1dd12ab09356a0e3b59fe93d57351df336cf311 | [log] [tgz] |
---|---|---|
author | Chris Craik <ccraik@google.com> | Thu Oct 19 09:06:48 2023 -0700 |
committer | Chris Craik <ccraik@google.com> | Wed Nov 15 15:00:04 2023 -0800 |
tree | 073f3559ce5c7133f24bcf1ac7bc3c2e0f6b9c94 | |
parent | 23f0f0ea24abada1b505f0c0c87211e81ce0c562 [diff] |
Break apart Compose benchmark runnables to avoid ANRs Bug: 300472956 Bug: 311256618 Bug: 311257475 Test: Manual/ABTD benchmark runs This changes ComposeBenchmarkRule and AndroidBenchmarkRule invocations from executing setup and benchmarks in a single runnable on the UI thread to instead work in batches on the UI thread. Reinstates some previously ignored benchmarks which scrolled via pointer events. This should drastically reduce the frequency of (locally hard to reproduce) ANRs in microbenchmarks in CI. In the future, this is a step toward preventing callers from running measureRepeated directly on the UI thread, as its target duration is 10 seconds - too long to block the UI thread. Change-Id: Ie40d84daf1f576ba31005f0b93887cd551b8a854
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.