This produces a chrome://tracing compatible trace file in the same way as -ftime-trace.
This can be useful in optimising test time where one long test is causing long overall test time on a wide machine.
This also helped in finding tests which have side effects on others (e.g. https://reviews.llvm.org/D84885).
Example:
2 blank lines