commit | ab01b93ac14c5cc6989089f3c1c1642d679df082 | [log] [tgz] |
---|---|---|
author | Chris Craik <ccraik@google.com> | Wed Apr 03 16:00:02 2024 -0700 |
committer | Chris Craik <ccraik@google.com> | Thu Apr 04 11:14:50 2024 -0700 |
tree | 5efa3114ca620f33985d35a8f1368ad01fba8df8 | |
parent | 27c066d47e7ca29ab8a659e8fc9126251bf3d740 [diff] |
Add profiler output files to JSON output Fixes:332604449 Test: ResultWriterTest Test: ./gradlew bench:b-c:cC bench:b-m:cC Relnote: "Added profilerOutput to JSON output for easier tooling around profiling traces (e.g. perfetto, method traces)" Add profiler output files to JSON. Outputs are file paths relative to the JSON file itself. If we add an option for per-test JSON files, these will stay the same. The ProfilerOutput vs Profiler.ResultFile layering is a bit awkward. Over time, we'll likely want a better layering, with a intermediate (potentially public API compatible) layer above the JSON type, similar to the old BenchmarkResult. Benchmark tests will output that, which can emit JSON via json.BenchmarkData, or InstrumentationResults directly. This would simplify a lot of the result type conversions, and remove references to json from everywhere but that top level output type. Change-Id: I05ddd9af8864fdb79ce076e836699b80fca864e6
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.