Andrew Gunnerson
7d0bb378a6
rawzip is a lower-level zip file library that is much more suited for avbroot's use case. Its speed improvements aren't too important since OTAs only have a handful of files, but it is a simpler layer of abstraction and exposes more about zip file internals. We also no longer need to maintain a perpetual fork of the zip library. The only caveat is that rawzip (much like avbroot) is built around writing zip files in a streaming fashion. To support `--zip-mode seekable`, the output file is post-processed to copy the relevant data descriptor fields to the local header. The unused data descriptors remain in the file to avoid needing to shift file data, but this does not violate the spec and Android's libziparchive accepts it just fine. Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>
End-to-end tests
avbroot's output file is reproducible for a given input file. e2e.toml lists some profiles for generating mock OTA images with unique properties and the expected checksums before and after patching. These tests use pregenerated, hardcoded test keys for signing. These keys should NEVER be used for any other purpose.
For each profile listed in the config, the test process will:
- Generate a mock OTA based on the specification
- Verify tha original OTA checksum
- Run avbroot against the OTA using
--magisk(with a mock Magisk APK) - Verify the patched OTA checksum
- Extract the AVB-related partitions from the patched OTA
- Run avbroot against the OTA again using
--prepatched - Verify the patched OTA checksum again
The default profiles shipped with the project mimic how various stock OTAs for Pixel devices are built. The generated mock OTAs have valid signatures and data structures for all components, but without any actual data where possible. For example, most files in the ramdisks are empty files. To ensure the mock OTAs cannot be mistakenly installed on a real device, the OTA metadata lists a fake device name in the preconditions section.
Running the tests
To test against the profiles listed in e2e.toml, run:
# To test all profiles
cargo run --release -- test -a
# Or to test against specific profiles
cargo run --release -- test -p pixel_v4_gki -p pixel_v4_non_gki