TraceWriterForTesting: clean up old single-proto assumptions

Before the patch that introduced the TODO, the TraceWriterForTesting
wasn't respecting trace packet boundaries, and was always returning
one merged proto. The android log tests only cared about the contents
of the first packet, that assumption is now more explicit.

Also, changing the single-packet accessor to be more convenient to use:
* simpler return type (the packet proto)
* internal assertion that there's indeed only one packet

Change-Id: Iceee2df3bca1bd4a4fec6c21ce2595ed9a31dc4c
5 files changed
tree: cf73da9ae8928423706d450cb15b4f6009b1e7e2
  1. build_overrides/
  2. buildtools/
  3. debian/
  4. docs/
  5. gn/
  6. include/
  7. infra/
  8. protos/
  9. src/
  10. test/
  11. tools/
  12. ui/
  13. .clang-format
  14. .gitignore
  15. .gn
  16. .travis.yml
  17. Android.bp
  18. Android.bp.extras
  19. BUILD
  20. BUILD.extras
  21. BUILD.gn
  22. codereview.settings
  23. heapprofd.rc
  24. MODULE_LICENSE_APACHE2
  25. NOTICE
  26. OWNERS
  27. perfetto.rc
  28. PRESUBMIT.py
  29. README.chromium
  30. README.md
  31. TEST_MAPPING
README.md

Perfetto - Performance instrumentation and tracing

Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.

See www.perfetto.dev for docs.

Bugs

  • For bugs affecting Android or the tracing internals use the internal bug tracker (go/perfetto-bugs).
  • For bugs affecting Chrome use http://crbug.com, Component:Speed>Tracing label:Perfetto.