Always set bad_message_reason when logging bad message dumps

Always set bad_message_reason when logging bad message dumps

The crash key was accidentally left unset when bad message dumps
were moved to the IO thread. This fixes that.

BUG=680542
R=creis@chromium.org

Review-Url: https://codereview.chromium.org/2629773002
Cr-Commit-Position: refs/heads/master@{#443440}
Committed: https://chromium.googlesource.com/chromium/src/+/d29667992640dc24a65202828f64e7517aa5aba0

[Ken Rockot(use gerrit already), 2017-01-13 00:32:08]

The CQ bit was checked by rockot@chromium.org to run a CQ dry run

[Ken Rockot(use gerrit already), 2017-01-13 00:33:28]

The CQ bit was checked by rockot@chromium.org to run a CQ dry run

[Ken Rockot(use gerrit already), 2017-01-13 00:33:31]

Patchset #1 (id:1) has been deleted

[commit-bot: I haz the power, 2017-01-13 00:34:08]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Charlie Reis, 2017-01-13 00:44:07]

Much appreciated!  LGTM.

[Ken Rockot(use gerrit already), 2017-01-13 00:45:07]

The CQ bit was unchecked by rockot@chromium.org

[Ken Rockot(use gerrit already), 2017-01-13 00:45:08]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2017-01-13 00:45:44]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-13 01:36:51]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1484268308271410,
"parent_rev": "4b184ca093fba8aabfccdba8391c3676815beed9", "commit_rev":
"d29667992640dc24a65202828f64e7517aa5aba0"}

[commit-bot: I haz the power, 2017-01-13 01:37:41]

Description was changed from

==========
Always set bad_message_reason when logging bad message dumps

The crash key was accidentally left unset when bad message dumps
were moved to the IO thread. This fixes that.

BUG=680542
R=creis@chromium.org
==========

to

==========
Always set bad_message_reason when logging bad message dumps

The crash key was accidentally left unset when bad message dumps
were moved to the IO thread. This fixes that.

BUG=680542
R=creis@chromium.org

Review-Url: https://codereview.chromium.org/2629773002
Cr-Commit-Position: refs/heads/master@{#443440}
Committed:
https://chromium.googlesource.com/chromium/src/+/d29667992640dc24a65202828f64...
==========

[commit-bot: I haz the power, 2017-01-13 01:37:42]

Committed patchset #1 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/d29667992640dc24a65202828f64...