commit | d05a9f4c7886d723f2182c1e11c941633c7e98f4 | [log] [tgz] |
---|---|---|
author | Sven Zheng <svenzheng@google.com> | Mon May 06 17:25:27 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 06 17:25:27 2024 |
tree | a3f1eaa417cc841bb440dd59d77f7aa5d3e250a2 | |
parent | a92ff7453f1be7de10fd81b7d9bf4245c9a3fc64 [diff] |
Get bisect_builds.py supporting Android Currently there are 3 scripts in different repos, all doing bisection. The goal is to unify them to 1 script, to simplify the usage and maintenance. See go/chrome-bisection-refresh. Specifically for Clank, it's mentioned in 3 scripts: https://source.chromium.org/chromium/chromium/src/+/main:tools/bisect-builds.py;l=196;drc=0826fa9ec336323b6c73bc41ec7c923f014437ac https://chrome-internal.googlesource.com/chrome/test/python_tests/+/refs/heads/main/bisect_builds.py#177 Eventually I would like to delete bisect-archived-builds.py in clank/tools. Bisection for any platform would use chromium/src/tools/bisect/bisect_builds.py. This change merges a few changes in bisect-archived-builds.py to support official bisection. Release bisection will be added in the next cl. python3 bisect_builds.py -b 126.0.6436.0 -g 126.0.6435.0 -a android-arm64 --device <> -o --apk chrome python3 bisect_builds.py -b 126.0.6436.0 -g 126.0.6435.0 -a android-arm --device <> -o --apk chrome python3 bisect_builds.py -b 126.0.6436.0 -g 126.0.6435.0 -a android-arm64 --device <> -o --apk system_webview_google Test: Bug: b:331228820 Change-Id: Iccc7edf8d86ae4c60b025bb7a2ded14456d5ffef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5503850 Commit-Queue: Sven Zheng <svenzheng@chromium.org> Reviewed-by: Mohamed Heikal <mheikal@chromium.org> Reviewed-by: Peter Wen <wnwen@chromium.org> Cr-Commit-Position: refs/heads/main@{#1296928}
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.