Tweak tracing JSON output formatting.

Tweak tracing JSON output formatting.

- \n between events
- move category field past ones having a fixed width.

Committed: https://crrev.com/4feef6baa415f8616ad2f93041e3437899996d4b
Cr-Commit-Position: refs/heads/master@{#311301}

[alph, 2014-12-22 13:59:06]

alph@chromium.org changed reviewers:
+ dsinclair@chromium.org, yurys@chromium.org

[yurys, 2014-12-22 15:23:34]

lgtm

[dsinclair, 2015-01-05 14:59:24]

Is there a reason to do this, or is it to just make the output look nicer?

[yurys, 2015-01-13 10:19:49]

On 2015/01/05 14:59:24, dsinclair wrote:
> Is there a reason to do this, or is it to just make the output look nicer?

This is just to make the trace file easier to read as each event is now on its
own line.

[alph, 2015-01-13 10:30:29]

On 2015/01/13 10:19:49, yurys wrote:
> On 2015/01/05 14:59:24, dsinclair wrote:
> > Is there a reason to do this, or is it to just make the output look nicer?
> 
> This is just to make the trace file easier to read as each event is now on its
> own line.

Yes. vim and less run very laggy on files without EOLs.

[dsinclair, 2015-01-13 14:18:48]

On 2015/01/13 at 10:30:29, alph wrote:
> On 2015/01/13 10:19:49, yurys wrote:
> > On 2015/01/05 14:59:24, dsinclair wrote:
> > > Is there a reason to do this, or is it to just make the output look nicer?
> > 
> > This is just to make the trace file easier to read as each event is now on
its
> > own line.
> 
> Yes. vim and less run very laggy on files without EOLs.

True but that's pretty easy to fix with a s/},{/},\n{/ after the fact. How much
larger do the trace files get if we do this?

[dsinclair, 2015-01-13 14:18:58]

dsinclair@chromium.org changed reviewers:
+ nduca@chromium.org

[alph, 2015-01-13 14:23:29]

On 2015/01/13 14:18:48, dsinclair wrote:
> On 2015/01/13 at 10:30:29, alph wrote:
> > On 2015/01/13 10:19:49, yurys wrote:
> > > On 2015/01/05 14:59:24, dsinclair wrote:
> > > > Is there a reason to do this, or is it to just make the output look
nicer?
> > > 
> > > This is just to make the trace file easier to read as each event is now on
> its
> > > own line.
> > 
> > Yes. vim and less run very laggy on files without EOLs.
> 
> True but that's pretty easy to fix with a s/},{/},\n{/ after the fact. How
much
> larger do the trace files get if we do this?

Sure, but it's not too convenient.
~1% I guess.

[dsinclair, 2015-01-13 17:45:05]

The CQ bit was checked by dsinclair@chromium.org

[dsinclair, 2015-01-13 17:45:05]

lgtm

[commit-bot: I haz the power, 2015-01-13 17:45:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/821033002/1

[commit-bot: I haz the power, 2015-01-13 19:01:01]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-13 19:02:21]

Patchset 1 (id:??) landed as
https://crrev.com/4feef6baa415f8616ad2f93041e3437899996d4b
Cr-Commit-Position: refs/heads/master@{#311301}