commit | 25a60acbe4cb2d409f030dbb6a0d51ef5d0d51b4 | [log] [tgz] |
---|---|---|
author | Peter Wen <wnwen@chromium.org> | Wed Mar 05 16:57:10 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 05 16:57:10 2025 |
tree | a217d8833faaa06d47ed7b3b777c57e6aa473621 | |
parent | 91fab14eb5e33c5889db13daddf0b04f4023bc84 [diff] |
android: Add GN dependency graph to stats Previously only the actual jdeps graph was used, and it was missing additional deps that are only in GN. This CL also parses the GN target dep from project.json. The script now requires passing `-C` or `--out-dir` for the output directory in which to generate project.json. Skip testonly targets and targets with 'test' in their name by default. Pass --include-testonly to add them back. Add some targets that the annotator regularly misses (e.g. annotations, errorprone, profiling) as these are not blockers for other targets to be annotated. Allow verbose output to show more information about each target and which other targets they depend on. Improve transitive dep detection to account for up to 2^5 = 32 deep dep-chains. i.e. A1 depends on A2 ... depends on A32 should all be resolved in the transitive dep graph correctly. Takes less than 2 minutes with --no-cache, and 15 seconds with a full cache (i.e. /tmp files and existing project.json file). R=hnakashima@chromium.org Bug: 389129271 Change-Id: I565c682e2e5b3bf96f1a76e47c0449479b9e1796 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6329736 Auto-Submit: Peter Wen <wnwen@chromium.org> Reviewed-by: Henrique Nakashima <hnakashima@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/main@{#1428366}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.