commit 15ea5dfe013e01af2b66e01ec20835ec61222692
author Eric Seckler <eseckler@google.com> Mon Oct 14 13:54:07 2019 +0100
committer Eric Seckler <eseckler@google.com> Mon Oct 14 12:56:04 2019 +0000
tree 2730be3a50bce1ea6ade7815e1c2f67e3c4dffda
parent dbb94e26f6507809b9f55482482c5da127bf9ef7

processor: Translate track & chrome event timestamps to trace time

As a short-term workaround, consider timestamps inside track events as
MONOTONIC domain timestamps. Chrome writes MONOTONIC timestamps on
Android (*) and is the only real user of this timestamp field at the
moment.

Longer term, Chrome will move to writing timestamps in the trace
packet directly, and set the timestamp_clock_id accordingly.

Also includes a hack to treat chrome events / metadata timestamps as
monotonic by default. Chrome already sets these timestamp fields, but
is still missing to set the clock_id due to a bug in chrome. We will
fix this in Chrome too, but should still preserve the ability to
import the buggy trace files correctly for the time being.

(*) Note that Chrome-only traces don't contain clock snapshots right
now, so this change will only affect system + chrome traces, which are
currently only supported on Android.

Bug: 138819158
Change-Id: Ib0a1c7f37f96d6499230b0ed298d43f9b537b318