| commit | 79d675b99c20c2b3066e5506e2a6b5a3501934d1 | [log] [tgz] |
|---|---|---|
| author | Jaewan Kim <jaewan@google.com> | Thu Jul 25 18:09:49 2024 +0900 |
| committer | Jaewan Kim <jaewan@google.com> | Thu Jul 25 21:50:44 2024 +0900 |
| tree | 0cf686a902139a829f5da27984b130665111acce | |
| parent | 58acbd04acacdb78ba925923a2557f7cb7c3d7fe [diff] |
vm_accessor_test: Redirect VM log to logcat
Even though this CL redirects VM log to logcat,
we can't see it directly with atest.
It's because teardown reboots the device,
so we need a way to see logcat after the test is over.
Here's two options (except for modifying AndroidTest.xml)
- Disable test teardown:
`atest -d vm_accessor_test; atest -t vm_accessor_test`
I don't know why, but both IAccessor implementation nor
VM don't print any log for the first `atest -d`.
But it would be a separated issue.
- Check logcat at `/tmp/atest_result_${USER}/LATEST/`
Test: Manually
Change-Id: Ic4ce8265413fca57c4c326a622ded1ceafd498a2
Android Virtualization Framework (AVF) provides secure and private execution environments for executing code. AVF is ideal for security-oriented use cases that require stronger isolation assurances over those offered by Android’s app sandbox.
Visit our public doc site to learn more about what AVF is, what it is for, and how it is structured. This repository contains source code for userspace components of AVF.
If you want a quick start, see the getting started guideline and follow the steps there.
For in-depth explanations about individual topics and components, visit the following links.
AVF components:
AVF APIs:
How-Tos: