Calculate broken tests threshold based on number of tests in binary, before applying filter

Calculate broken tests threshold based on number of tests in binary, before applying filter

BUG=none

Committed: https://crrev.com/a81b650f85ebbeba0270d17f566bccffa4988394
Cr-Commit-Position: refs/heads/master@{#361607}

[Paweł Hajdan Jr., 2015-11-24 12:43:51]

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

[Paweł Hajdan Jr., 2015-11-24 12:43:51]

See e.g.
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...
for context.

It seems to me the current check is too strict, especially when we run a small
list of tests.

As a possible alternative approach, I could make the recipes pass a flag to the
test launcher disabling this behavior when we run tests without the patch. The
number of tests retried that way would by design be limited.

[sky, 2015-11-24 16:35:54]

LGTM

[Paweł Hajdan Jr., 2015-11-25 08:02:38]

The CQ bit was checked by phajdan.jr@chromium.org

[commit-bot: I haz the power, 2015-11-25 08:02:46]

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

[commit-bot: I haz the power, 2015-11-25 08:07:28]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-25 08:08:13]

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