Tests are no longer sensitive to where the logs are from

A Microdroid VM emits logs via two serial ports. The first serial port
is used as the console where kernel logs (and userspace logs sent to
/dev/kmsg) are emitted. The second serial port is used for the logs
emitted via liblog.

There are some tests which expect certain string (ex: boot complete
message) from the VM logs. The problem however was that those tests have
had knowwledge about which of the two serial ports to read. This broke
the tests when we changed where the logs are emitted to.

With this change, the tests are no longer sensitive to where the logs
are from.

Bug: 308383728
Test: run against git_24Q1-release
Change-Id: Ie98acc8e64e157211fe3bfd0b37f66972726887c
2 files changed
tree: 31930e954d2394e33117555d951839ae341964ee
  1. apex/
  2. apkdmverity/
  3. authfs/
  4. compos/
  5. demo/
  6. demo_native/
  7. docs/
  8. encryptedstore/
  9. javalib/
  10. launcher/
  11. libs/
  12. microdroid/
  13. microdroid_manager/
  14. pvmfw/
  15. rialto/
  16. secretkeeper/
  17. service_vm/
  18. tests/
  19. virtualizationmanager/
  20. virtualizationservice/
  21. vm/
  22. vm_payload/
  23. vmbase/
  24. vmclient/
  25. zipfuse/
  26. .clang-format
  27. .gitignore
  28. Android.bp
  29. OWNERS
  30. PREUPLOAD.cfg
  31. README.md
  32. rustfmt.toml
  33. TEST_MAPPING
README.md

Android Virtualization Framework (AVF)

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: