Make verdict optional in csd proto.

Since the verdict field is currently marked as 'required', whenever Chrome (or Firefox) can't parse this field properly, it leads to an overall failure in parsing the entire proto message.

Making it optional with a default value (SAFE) solves that problem.

See: cl/131841696

BUG=

Committed: https://crrev.com/1596433b53b1829f1a28306d0a995fe285afe926
Cr-Commit-Position: refs/heads/master@{#415771}

[vakh (use Gerrit instead), 2016-08-31 17:32:34]

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

[commit-bot: I haz the power, 2016-08-31 17:32:55]

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

[vakh (use Gerrit instead), 2016-08-31 17:33:05]

vakh@chromium.org changed reviewers:
+ jialiul@chromium.org, noelutz@chromium.org, nparker@chromium.org

[Jialiu Lin, 2016-08-31 17:43:54]

lgtm

[commit-bot: I haz the power, 2016-08-31 18:31:27]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-31 18:31:28]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[vakh (use Gerrit instead), 2016-08-31 21:18:13]

Update the unit test to use SAFE as the default value when encountering an
invalid value.

[vakh (use Gerrit instead), 2016-08-31 21:18:15]

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

[commit-bot: I haz the power, 2016-08-31 21:19:12]

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

[vakh (use Gerrit instead), 2016-08-31 21:21:15]

Description was changed from

==========
Make verdict optional. See: cl/131841696

BUG=
==========

to

==========
Make verdict optional. See: cl/131841696

BUG=
==========

[vakh (use Gerrit instead), 2016-08-31 21:23:30]

Description was changed from

==========
Make verdict optional. See: cl/131841696

BUG=
==========

to

==========
Since the verdict field is currently marked as 'required', whenever Chrome (or
Firefox) can't parse this field properly, it leads to an overall failure in
parsing the entire proto message.

Making it optional with a default value (SAFE) solves that problem. 

See: cl/131841696

BUG=
==========

[vakh (use Gerrit instead), 2016-08-31 21:24:04]

The CQ bit was checked by vakh@chromium.org

[vakh (use Gerrit instead), 2016-08-31 21:24:04]

The patchset sent to the CQ was uploaded after l-g-t-m from jialiul@chromium.org
Link to the patchset: https://codereview.chromium.org/2292963004/#ps20001
(title: "Update the unit test to use SAFE as the default value when encountering
an invalid value.")

[commit-bot: I haz the power, 2016-08-31 21:24:46]

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, 2016-08-31 22:06:23]

Description was changed from

==========
Since the verdict field is currently marked as 'required', whenever Chrome (or
Firefox) can't parse this field properly, it leads to an overall failure in
parsing the entire proto message.

Making it optional with a default value (SAFE) solves that problem. 

See: cl/131841696

BUG=
==========

to

==========
Since the verdict field is currently marked as 'required', whenever Chrome (or
Firefox) can't parse this field properly, it leads to an overall failure in
parsing the entire proto message.

Making it optional with a default value (SAFE) solves that problem. 

See: cl/131841696

BUG=
==========

[commit-bot: I haz the power, 2016-08-31 22:06:24]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-08-31 22:09:11]

Description was changed from

==========
Since the verdict field is currently marked as 'required', whenever Chrome (or
Firefox) can't parse this field properly, it leads to an overall failure in
parsing the entire proto message.

Making it optional with a default value (SAFE) solves that problem. 

See: cl/131841696

BUG=
==========

to

==========
Since the verdict field is currently marked as 'required', whenever Chrome (or
Firefox) can't parse this field properly, it leads to an overall failure in
parsing the entire proto message.

Making it optional with a default value (SAFE) solves that problem.

See: cl/131841696

BUG=

Committed: https://crrev.com/1596433b53b1829f1a28306d0a995fe285afe926
Cr-Commit-Position: refs/heads/master@{#415771}
==========

[commit-bot: I haz the power, 2016-08-31 22:09:12]

Patchset 2 (id:??) landed as
https://crrev.com/1596433b53b1829f1a28306d0a995fe285afe926
Cr-Commit-Position: refs/heads/master@{#415771}