... also fixed missing copyright headers in 2 existing test files
... also made the instrumentation against the demo activity for real
Bug: 277819423
Test: atest FlagStateComboTests
adb shell device_config put test \
com.example.android.aconfig.demo.flags.awesome_flag_1 <true|false>
adb shell device_config put test \
com.example.android.aconfig.demo.flags.awesome_flag_2 <true|false>
Change-Id: I6083f11ee743a8b4f0f9bc23ac6945b5d072ab5e
The script must fail and be excluded from the build stats if any
build run fails.
Bug: 284915566
Test: run_command with fault command
Change-Id: I0bc8d14286ebce52036f45ba4dee675f333a3ff0
verbose.log.gz includes the logs for the ninja explain.
The logs will be automatically cached to verbose.log.gz,
verbose.log.2.gz, and verbose.log.4.gz.
Bug: 284915566
Test: combined_build_test.sh -t cf_x86_64_phone -v userdebug \
-d out/dist -a cf_x86_64_foldable -o -c -r droid
Change-Id: Ib722a7c331cfe6b034ab4812b85504d2f5161881
VNDK snapshot updater reads license text files. To avoid unexpected
text files to be read, explicitly set the encoding type and ignore
if failed to read.
Bug: 288846788
Test: add binary to read and see if it is ignored
Change-Id: I7e3d0bbdc6c692ef7dbc6d8bf9d53c67003d0f90
So we have a way to play with the android.net.http APIs.
This is essentially copied from
https://source.chromium.org/chromium/chromium/src/+/main:components/cronet/android/sample/
with minor modifications to support android.net.http APIs (mainly,
renaming APIs and working around the fact that apihelpers are not
available to apps).
Test: adb install -r $OUT/system/app/Development/Development.apk
Change-Id: I8fdb2f64f110551edd39fab074abaf84e76b010f
This commit fixes the bug that causes the ABI tools to produce invalid
output but return success.
Bug: 288168134
Test: development/vndk/tools/header-checker/tests/test.py
Change-Id: Ifa94667e9d38eff65e943a1d277dd2c7b5493fe5
Add the Injection use case of Aconfig flag.
Add corresponding tests.
Test: atest AconfigDemo_ContentLibs_Test
Bug: 287644619
Change-Id: I47cea59764b2956644ad0c159945d3cdb3231c09
Add a simple app uses aconfig.
This app can demonstrate
1. declare aconfig flag
2. build aconfig flag in building system
3. generate aconfig java flag
4. use aconfig java flag in java code
Test: atest AconfigDemo_ContentProvide_Test
Bug: 280833426
Change-Id: Ieacbe4b2368a00872254dab1c87dc66c569fc30a
The current cargo2android.py doesn't work well w/ `--cargo_bin`. It would use the full path rustc(/<HOME>/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustc) instead of basename(`rustc`). The `RUSTC_PAT` and `RUSTC_VV_CMD_ARGS` regex doesn't match the full path.
This CL uses `(.*\/)?` to match the path if it exists.
Change-Id: If5e4060410c1cd45ad6c9612ebe856552aa14d08
They consume much disk space even though they are not used.
Bug: 284915566
Test: combined_build_test.sh -t cf_x86_64_phone -v userdebug \
-d out/dist -a cf_x86_64_foldable -o -c droid
Change-Id: I4fd5e9326e5c77c28c5e178f63ba396c9e462cbd
The Aconfig demo will be used as
1. As an example for aconfig code lab
2. As an example for user to learn Aconfig
Test: N/A
Bug: 287644619
Change-Id: Ida6c922fdd52caaecfadff99809a70fab8442814
Add the path to the existing architecture-specific runtime directory,
in preparation for when lldb-server is added to the toolchain build by
Iba7efaa62e7d3cc8e3bd1080d9b4a67bc241faf2.
Test: `gdbclient.py -r surfaceflinger` connected to a riscv64 board
Change-Id: I1654378a7ba92fcd7ffe478d2b491f426655e6f1
Redshell unfortunately uses this old version, while the union operator
for dictionaries was only added in Python 3.9.
Test: Ran cargo2android.py on a crate with variants
Change-Id: I7a875acde11c23a3b789ef384f3ab32100d7c6d5
Enable multiple test builds in one command and collect the results
from the build.trace.gz files.
Bug: 284915566
Test: combined_build_test.sh -t cf_x86_64_phone -v userdebug \
-d out/dist -a cf_x86_64_foldable -o -c droid
Change-Id: Ie566fd76463aa615c37130f4c4c7b8287fd8c447
The new argument allows the user to pass a JSON of properties to merge
into the generated launch.json config when setting up vscode-lldb
forwarding. This way the user can add pre-build tasks, extra init
commands etc.
Test: atest gdbclient_test
Test: lldbclient.py --setup-forwarding=vscode-lldb
--vscode-launch-props='{"sourceMap": {"test1": "test2"},
"postDebugTask": "Stop LLDB client", "processCreateCommands" :
["test"]}' -r test
Change-Id: I763dd15dde10421e86bc0a6ddfde974156ef1588
