Bug: 151896491
Test: presubmit check
Exempt-From-Owner-Approval: This CL renames suite name vts-core to vts.
It won't change test logic or behavior.
Change-Id: I79cddf5e4a65486b8f1286ea430360479ad2b93d
This module itself is not a test, but an executable to run by another
test.
Test: TH
Bug: 152437576
Change-Id: Id6561278879f5eb7d900dd5b6f6a6c90189fefb6
CDD requires new devices launching with R to support fs-verity.
Test: `atest ApkVerityTest` on device with first_api_level=30
Bug: 150641206
Change-Id: Ied831fa720fecc623dbac6bdbd1263856d2792ef
VTS provides rootable environment for ApkVerityTest to run.
ApkVerityTest needs to write block device to verify the failure case of
fs-verity.
Test: see ApkVerityTests and block_device_writer in `unzip -l
out/host/linux-x86/vts-core/android-vts-core.zip`
Bug: 150641206
Change-Id: Idc71907a28f68fc873c5cac940aa706e0b79843e
The previous known directories seem to be removed in some case and
breaks the test. Since the intention is to exclude directories and
compare existing files, exclude all directories instead.
Test: atest ApkVerityTest
Bug: 149469433
Change-Id: Ib096062b5647920b90f7d9d5638226392a2df174
The test has been green for weeks. Promoting to presubmit.
Test: atest --test-mapping
Bug: 112039386
Change-Id: I3452335c1d0935a929e1ced7f9581496203b4fcb
Without this change, the verifier may hold the fd of installed apk and
prevents the cache eviction. The existing retry loop up to 5 seconds is
not sufficient.
Also removed an obsolete verifier setting.
Test: com.android.apkverity.ApkVerityTest#testInstallSplitOnly succeeded
100% (75+ times).
Bug: 146350859
Change-Id: Ia7d42ab6efcb42de83626f1d63bff5a8adc6c1a6
This adds more visibility to when the cache was not evicted for some
reasons.
Test: run atest, saw the log
Bug: 146350859
Change-Id: I926c9702ff5540ff8291f447d14559fcf5f8395e
By keeping block_device_writer_module in target_required, it avoids
build error of "missing variant: os:linux_glibc, arch:common", while
the test still run on forrest.
Test: forrest
Test: lunch flame-eng; atest ApkVerityTest
Test: lunch aosp_x86_64-eng; m ApkVerityTest
Bug: 112039386
Change-Id: I9cfa0928941b008e23c2a32bb47dae5369bd3201
This allows pread/pwrite to access big storage.
Test: run the command, see expected behavior
Bug: 144164497
Change-Id: Ie560da4fc44f8bd10c332629ac9732053990f808
The backing block on disk could be relocated by f2fs. Pinning the file
to avoid corrupting the filesystem.
Test: atest com.android.apkverity.ApkVerityTest
Bug: 112039386
Change-Id: Ieed78d78e948fc38df1c6c654ec55573f9a13543
There are two categories of tests:
1. Package installation with .fsv_sig
* .apk, .dm, including the split ones should all or none be installed
with their corresponding .fsv_sig files
2. End-to-end fs-verity test of on-access verification
* When fs-verity is enabled to a file, if the on-disk content is
changed, the read should fail.
See class comment in ApkVerityTest.java for the test details.
Brief directory layout overview:
* src/
- Actual test
* ApkVerityTestApp/
- Dummy app for testing, including a split
* testdata/
- Some artifacts, signing key and fs-verity signatures
* block_device_writer/
- Helper binary for write a file directly on disk
Test: atest
Bug: 112039386
Change-Id: I3b8229037db682f36fda9d5cafd14caf6b39501d
