Presubmit for chrome/browser/resources matches multiline metric types.

Presubmit for chrome/browser/resources matches multiline metric type.

Also added a testcase for it and a nice print of errors.

BUG=443026
Committed: https://crrev.com/940df072ba1d09a1095d3c67bb5d06d6b1a4ba02
Cr-Commit-Position: refs/heads/master@{#317794}

[gayane -on leave until 09-2017, 2014-12-18 19:51:40]

gayane@chromium.org changed reviewers:
+ michaelpg@chromium.org

[gayane -on leave until 09-2017, 2014-12-18 19:53:37]

gayane@chromium.org changed reviewers:
+ phajdan.jr@chromium.org

[gayane -on leave until 09-2017, 2014-12-18 19:53:38]

Please have a look.

[michaelpg, 2014-12-19 21:49:04]

lgtm, it fixes the issue but I can't be sure this works for everything.

[gayane -on leave until 09-2017, 2014-12-22 16:54:09]

gayane@chromium.org changed reviewers:
+ dbeam@chromium.org

[gayane -on leave until 09-2017, 2014-12-22 16:54:09]

dbeam@chromium.org: Please have a look for owners review 
-PRESUBMIT.py 
-PRESUBMIT_test.py

[Dan Beam, 2014-12-31 02:01:07]

lgtm

[gayane -on leave until 09-2017, 2014-12-31 06:48:13]

The CQ bit was checked by gayane@chromium.org

[commit-bot: I haz the power, 2014-12-31 06:48:22]

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

[commit-bot: I haz the power, 2014-12-31 06:54:33]

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

[commit-bot: I haz the power, 2014-12-31 06:54:34]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[gayane -on leave until 09-2017, 2015-01-07 15:46:22]

phajdan.jr@chromium.org: Would you do the owners review for
PRESUBMIT_test_mocks.py.

[Paweł Hajdan Jr., 2015-01-07 16:41:12]

https://codereview.chromium.org/809053003/diff/1/PRESUBMIT_test_mocks.py
File PRESUBMIT_test_mocks.py (right):

https://codereview.chromium.org/809053003/diff/1/PRESUBMIT_test_mocks.py#newc...
PRESUBMIT_test_mocks.py:57: return self.message
Why is this needed?

[gayane -on leave until 09-2017, 2015-01-07 16:57:15]

On 2015/01/07 16:41:12, Paweł Hajdan Jr. wrote:
> https://codereview.chromium.org/809053003/diff/1/PRESUBMIT_test_mocks.py
> File PRESUBMIT_test_mocks.py (right):
> 
>
https://codereview.chromium.org/809053003/diff/1/PRESUBMIT_test_mocks.py#newc...
> PRESUBMIT_test_mocks.py:57: return self.message
> Why is this needed?

In case the presubmit results are not as expected I print them in unittests. 


For example in chrome/browser/resources/PRESUBMIT_test.py:59

    self.assertEqual(1, len(warnings), warnings)

where warnings have type PresubmitPromptWarning.

[michaelpg, 2015-02-24 07:27:20]

ping: although the regexes aren't perfect, this is a step in the right
direction, right?

[Paweł Hajdan Jr., 2015-02-24 13:18:22]

LGTM

[gayane -on leave until 09-2017, 2015-02-24 14:18:19]

The CQ bit was checked by gayane@chromium.org

[commit-bot: I haz the power, 2015-02-24 14:18:35]

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

[commit-bot: I haz the power, 2015-02-24 14:28:37]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-24 14:29:13]

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