trace_processor: print non-zero error stats and stop counter events from log spam

While the stats table is very important for putting data that we consider
important context to trace analysis, often people can overlook looking at
it until after some significant investigation has been done. This can lead
to frustration that these stats were not surfaced earlier.

Change this by querying stats at the end of importing the trace in trace
processor shell and printing it out to stderr. This allows users to see if their
trace is busted/trace processor has a bug before they get into proper analysis.

And since we have stats for this now and print them in shell,
turn the ELOG into a DLOG for counter out of order
to avoid log spam if this does happen.

Bug: 126443808
Change-Id: I2cdb7e2710242d044c78f729c004ab93c38fcc90
2 files changed
tree: 701a13d44ddebba72e7e3d54d8115b58ffb015f0
  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.