TraceProcessor: add ninja log parsing

Adds a parser for ninja build logs. This is the
moral equivalent of https://github.com/nico/ninjatracing.
This works only as long as ninja doesn't hit recompaction.
The log seems to stop making sense after re-compaction because
it becomes impossible to reconstruct the boundaries of
each build invocation.
I eye-balled this vs ninjatracing on the same trace and
the results seem to make sense.

Bug: 149483774
Test: TraceProcessorIntegrationTest.NinjaLog
Change-Id: Ice9ac9d9fee6a94d78fb0fec997b3b3d36d3c02b
11 files changed
tree: d03868e6c5b5b5ade650a77c7ea8759ef5344c26
  1. bazel/
  2. build_overrides/
  3. buildtools/
  4. debian/
  5. docs/
  6. gn/
  7. include/
  8. infra/
  9. protos/
  10. src/
  11. test/
  12. tools/
  13. ui/
  14. .clang-format
  15. .gitignore
  16. .gn
  17. .style.yapf
  18. Android.bp
  19. Android.bp.extras
  20. BUILD
  21. BUILD.extras
  22. BUILD.gn
  23. codereview.settings
  24. heapprofd.rc
  25. LICENSE
  26. MODULE_LICENSE_APACHE2
  27. NOTICE
  28. OWNERS
  29. perfetto.rc
  30. PRESUBMIT.py
  31. README.chromium
  32. README.md
  33. TEST_MAPPING
  34. traced_perf.rc
  35. WORKSPACE
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.

Contributing

See /docs/contributing.md for instructions.

The source-of-truth repo is Android's Gerrit. The GitHub repo is a read-only mirror.

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.

Community

You can reach us on our Discord channel. If you prefer using IRC we have an experimental Discord <> IRC bridge synced with #perfetto-dev on Freenode.