One flag '-f' corresponds to one directory that stores a parsed report.
Bug: 296988808
Test: ./compare_cts_reports.py -r test_result_1.xml [test_result_2.xml] \
[-r report.zip] [-f parsed_dir_1/] [-f parsed_dir_2/] -m n -d output_dir/
Change-Id: I26310982dc8ef18f5dbfb1a8382ea3a600508fbe
This is cleaner than using .unwrap_or(true) wherever they are used.
Bug: 293289578
Test: atest cargo_embargo.test
Change-Id: I763adf0cc51721408adf55b966ed4304e2766c00
"target" refers to a target arch, a build target, or a make target.
This commit renames the class and the variables to avoid ambiguity.
Test: development/vndk/tools/header-checker/utils/create_reference_dumps.py \
-products aosp_x86_64 -release trunk_staging
Bug: 297542516
Change-Id: Icfb06e18333d56af802c74494c1d158f367026c9
This commit adds -release as a parameter to create_reference_dumps.py.
It is currently optional. Developers can use it to try different
release configurations.
Test: development/vndk/tools/header-checker/utils/create_reference_dumps.py \
-products aosp_x86_64 -release trunk_staging
Bug: 297542516
Change-Id: Ifb7001ed42dbb9f8d0dd8e6c9738be6d5ea2feca
The attributes tested_items and pass_rate are added for easier display in the
n_way_comparison function.
Bug: 296988808
Test: ./compare_cts_reports.py -r test_result_1.xml -r test_result_2.xml -m n \
-d output_dir
Change-Id: I1dc6bb9c33dfe5be879cbdc13f684bde123e5e71
The script uses Python match which was introduced
in Python 3.10. The sandbox only has 3.8, so we need
to remove match so the script can run.
Bug: 281857510
Test: Run in sandbox on bitflags crate
Change-Id: Id03b0e02f8593b551f2aca201fe0ed2659d58d21
* changes:
Split cargo_out into three modules.
Factor out functions to find package directory.
Add more doc comments and break up parse_cargo_out function.
The script allows adding more targets using -a option multiple time.
Only a single -a will test aba build as before, but adding multiple
-a options will build the targets in sequence.
Bug: 293821290
Test: combined_build_test.sh -t primary -v userdebug -d out_dist \
-a alter1 -a alter2 -a alter3 -c -o -r droid
Change-Id: I3bc4d2f0dad6bac7aa32b165ca667334f90eb83b
Assumptions:
1. The input report file can be a zip file result from a standard cts
test tool, or a test_result.xml
2. If there are multiple cts reports after the -r flag, it means to view
these files as one report. The script aggregates them according to the
same rules as b/293809772.
Bug: 296323842
Test: ./compare_cts_reports.py -r [a.zip, test_result_1.xml] -r [b.zip,
test_result_2.xml] -m [1, 2] [-d output_directory] [-o]
Change-Id: I885dd07cd40d38ba0c2ee1cb38570a926606a4d9
This change add demo for using test mode flag lib in
self-instrumentation tests.
There are two options.
The option 1 is to create two versions, prod and test, of the library
using flags. The prod version library uses prod flag lib, and the test
version library uses test flag lib.
The option 2 is to dynamically link to the flag lib in the library. The
flag lib is used as a stub lib and is just used for building purpose.
The in the finally binary which uses the library, the binary should
statically link to the right version of the flag lib.
Bug: 295561701
Test: atest AconfigDemoUnitTests1 && atest AconfigDemoUnitTests2
Change-Id: Ie571a260d9042933032c702095808dbf59d1697c
When --add3prf is set, `get_rust_pkg.py` script `cd` into the crate directory and run `add3prf.py`. However, `add3prf.py` doesn't exist in the newly downloaded crate directory. This CL ensures that we reference to the existing `add3prf.py` script.
Test: development/scripts/get_rust_pkg.py -add3prf -v -o /tmp tinyjson-2.5.1
Change-Id: I4273d4f2b6a1f353960adbbab9abbb96bf3e68f3
The `cargo` module has the output types, `cargo_out` has the code
specific to parsing cargo.out files, while `metadata` has the types to
parse cargo.metadata files.
Bug: 293289578
Test: atest cargo_embargo.test
Change-Id: I5a2e2871a48bf30a64f3ffbc84a160b0daa91b53
