| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| testdata/ | 14-Jan-2024 | - | 151 | 138 | ||
| OWNERS | D | 14-Jan-2024 | 61 | 4 | 3 | |
| README.md | D | 14-Jan-2024 | 928 | 25 | 19 | |
| abstract_build_file_handler.py | D | 14-Jan-2024 | 1.6 KiB | 47 | 23 | |
| custom_build_file_handler.py | D | 14-Jan-2024 | 1.2 KiB | 34 | 12 | |
| incremental_deqp.py | D | 14-Jan-2024 | 26 KiB | 718 | 561 | |
| incremental_deqp_test.py | D | 14-Jan-2024 | 8.6 KiB | 186 | 139 | |
| target_file_handler.py | D | 14-Jan-2024 | 1.9 KiB | 57 | 34 | |
| target_file_handler_test.py | D | 14-Jan-2024 | 2.2 KiB | 55 | 30 |
README.md
1# Note 2incremental-cts is an EXPERIMENTAL project. It's for analysis purpose only and is NOT meant to be used for approval runs. 3 4# Examples 5 6## Generate dEQP dependency 7This command will generate a dEQP dependency file named `dEQP-dependency.txt`: 8``` 9python3 incremental_deqp.py -s device_serial_number -t /path/to/test_resources 10--generate_deps_only 11``` 12 13## Check if current build could skip dEQP 14 15Before running this command, please create `extra_deqp_dependency.txt` file and 16copy it to test resources directory. `extra_deqp_dependency.txt` includes the 17dEQP dependencies that can't be detected by this tool such as firmwares. 18``` 19python3 incremental_deqp.py -s device_serial_number -t /path/to/test_resources 20-b /path/to/target_file 21``` 22 23Target file is an build artifact produced by Android build system, e.g. 24https://ci.android.com/builds/submitted/7230538/aosp_arm64-userdebug/latest/aosp_arm64-target_files-7230538.zip 25