Enable --trace-to-console in ChromeOS builds

Enable --trace-to-console in ChromeOS builds

--trace-to-console was not being exported to new Chrome instances across
restart requests and so tracing didn't work in signed-in sessions. Add it
to the white list.

Committed: https://crrev.com/832bcfaf04f0663200f896c52138af39f8f472ac
Cr-Commit-Position: refs/heads/master@{#364162}

[rjkroege, 2015-12-09 03:15:22]

rjkroege@chromium.org changed reviewers:
+ oshima@chromium.org

[rjkroege, 2015-12-09 03:15:23]

Related to our earlier discussion about why I wasn't seeing output. Add tracing
to the white list. PTAL.

[oshima, 2015-12-09 19:41:28]

lgtm

[rjkroege, 2015-12-09 19:43:37]

The CQ bit was checked by rjkroege@chromium.org

[commit-bot: I haz the power, 2015-12-09 19:46:22]

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

[commit-bot: I haz the power, 2015-12-09 21:42:58]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-12-09 21:43:49]

Description was changed from

==========
Enable --trace-to-console in ChromeOS builds

--trace-to-console was not being exported to new Chrome instances across
restart requests and so tracing didn't work in signed-in sessions. Add it
to the white list.
==========

to

==========
Enable --trace-to-console in ChromeOS builds

--trace-to-console was not being exported to new Chrome instances across
restart requests and so tracing didn't work in signed-in sessions. Add it
to the white list.

Committed: https://crrev.com/832bcfaf04f0663200f896c52138af39f8f472ac
Cr-Commit-Position: refs/heads/master@{#364162}
==========

[commit-bot: I haz the power, 2015-12-09 21:43:50]

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