tracing: Only compare timestamps from the same sequence

There are two different sequences in the test:
1. The sequence emitted by the tracing service.
2. The sequence emitted by the thread in the test.

The test tries to check that the clock snapshots are monotonic, but it
doesn't make sense to check two clock snapshots of two different
sequences, which will very likely be reordered (perfetto tries to read
a whole sequence before reading the next).

This fixes a failure in CI (msan, I could not reproduce locally) with
the error message:

```
[00:03:13] [ RUN      ] PerfettoApiTest/PerfettoApiTest.LegacyTraceEventsAndClockSnapshots/System
[00:03:13] [777.777] ng_service_impl.cc:1075 Configured tracing session 1, #sources:1, duration:500 ms, #buffers:1, total buffer size:1024 KB, total sessions:1, uid:1337 session name: ""
[00:03:13] ../../src/tracing/test/api_integrationtest.cc:4944: Failure
[00:03:13] Expected: (last_clock_ts[id].ts) <= (ts), actual: 4930745079518161 vs 4930745077415448
[00:03:13] This sequence:2 prev sequence:1 clock_id:6
[00:03:13] [  FAILED  ] PerfettoApiTest/PerfettoApiTest.LegacyTraceEventsAndClockSnapshots/System, where GetParam() = 2 (35 ms)
```

Change-Id: If493a2d45ff6258f23403bca072a1f58308f31ce
1 file changed
tree: 34532d7e90335b1e9f6741598d6e273175af3e19
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. debian/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. python/
  13. src/
  14. test/
  15. third_party/
  16. tools/
  17. ui/
  18. .clang-format
  19. .clang-tidy
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .gn
  24. .style.yapf
  25. Android.bp
  26. Android.bp.extras
  27. BUILD
  28. BUILD.extras
  29. BUILD.gn
  30. CHANGELOG
  31. codereview.settings
  32. DIR_METADATA
  33. heapprofd.rc
  34. LICENSE
  35. meson.build
  36. METADATA
  37. MODULE_LICENSE_APACHE2
  38. OWNERS
  39. perfetto.rc
  40. PerfettoIntegrationTests.xml
  41. persistent_cfg.pbtxt
  42. PRESUBMIT.py
  43. README.chromium
  44. README.md
  45. TEST_MAPPING
  46. traced_perf.rc
  47. WATCHLISTS
  48. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

Perfetto is a production-grade open-source stack for performance instrumentation and trace analysis. It offers services and libraries and for recording system-level and app-level traces, native + java heap profiling, a library for analyzing traces using SQL and a web-based UI to visualize and explore multi-GB traces.

See https://perfetto.dev/docs or the /docs/ directory for documentation.