scheduler: Avoid false alerts about expensive task blocking

scheduler: Avoid false alerts about expensive task blocking

This patch adjusts the logic for logging a console message when an
expensive task is blocked:

1. Don't log messages when all timer tasks are blocked (e.g., while
   waiting for a touchstart response). There's nothing the developer can
   do to avoid this type of blocking.

2. Only report blocking for tasks which exceed the 50ms RAIL threshold.
   These types of tasks are most likely to cause user visible jank.
   Lower blocking thresholds are also used for shorter periods of time,
   so shorter tasks are not likely to be deferred for a long time
   in any case.

3. Also mention network tasks in the log message.

BUG=613230
Committed: https://crrev.com/c66723959e9a37f1a5bbd821366a2ee24a9537c2
Cr-Commit-Position: refs/heads/master@{#396467}

[Sami, 2016-05-27 12:46:15]

Description was changed from

==========
scheduler: Avoid false alerts about expensive task blocking

This patch adjusts the logic for logging a console message when an
expensive task is blocked:

1. Don't log messages when all timer tasks are blocked (e.g., while
   waiting for a touchstart response). There's nothing the developer can
   do to avoid this type of blocking.

2. Only report blocking for tasks which exceed the 50ms RAIL threshold.
   These types of tasks are most likely to cause user visible jank.
   Lower blocking thresholds are also used for shorter periods of time,
   so shorter tasks are not likely to be deferred for a long time
   in any case.

3. Also mention network tasks in the log message.

BUG=613230
==========

to

==========
scheduler: Avoid false alerts about expensive task blocking

This patch adjusts the logic for logging a console message when an
expensive task is blocked:

1. Don't log messages when all timer tasks are blocked (e.g., while
   waiting for a touchstart response). There's nothing the developer can
   do to avoid this type of blocking.

2. Only report blocking for tasks which exceed the 50ms RAIL threshold.
   These types of tasks are most likely to cause user visible jank.
   Lower blocking thresholds are also used for shorter periods of time,
   so shorter tasks are not likely to be deferred for a long time
   in any case.

3. Also mention network tasks in the log message.

BUG=613230
==========

[Sami, 2016-05-27 12:46:15]

skyostil@chromium.org changed reviewers:
+ alexclarke@chromium.org

[Sami, 2016-05-27 12:46:29]

PTAL.

[Sami, 2016-05-27 12:46:29]

PTAL.

[alex clarke (OOO till 29th), 2016-05-27 12:54:29]

lgtm

[Sami, 2016-05-27 13:26:55]

The CQ bit was checked by skyostil@chromium.org

[commit-bot: I haz the power, 2016-05-27 13:27:06]

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

[commit-bot: I haz the power, 2016-05-27 14:50:58]

Description was changed from

==========
scheduler: Avoid false alerts about expensive task blocking

This patch adjusts the logic for logging a console message when an
expensive task is blocked:

1. Don't log messages when all timer tasks are blocked (e.g., while
   waiting for a touchstart response). There's nothing the developer can
   do to avoid this type of blocking.

2. Only report blocking for tasks which exceed the 50ms RAIL threshold.
   These types of tasks are most likely to cause user visible jank.
   Lower blocking thresholds are also used for shorter periods of time,
   so shorter tasks are not likely to be deferred for a long time
   in any case.

3. Also mention network tasks in the log message.

BUG=613230
==========

to

==========
scheduler: Avoid false alerts about expensive task blocking

This patch adjusts the logic for logging a console message when an
expensive task is blocked:

1. Don't log messages when all timer tasks are blocked (e.g., while
   waiting for a touchstart response). There's nothing the developer can
   do to avoid this type of blocking.

2. Only report blocking for tasks which exceed the 50ms RAIL threshold.
   These types of tasks are most likely to cause user visible jank.
   Lower blocking thresholds are also used for shorter periods of time,
   so shorter tasks are not likely to be deferred for a long time
   in any case.

3. Also mention network tasks in the log message.

BUG=613230
==========

[commit-bot: I haz the power, 2016-05-27 14:50:59]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-27 14:53:05]

Description was changed from

==========
scheduler: Avoid false alerts about expensive task blocking

This patch adjusts the logic for logging a console message when an
expensive task is blocked:

1. Don't log messages when all timer tasks are blocked (e.g., while
   waiting for a touchstart response). There's nothing the developer can
   do to avoid this type of blocking.

2. Only report blocking for tasks which exceed the 50ms RAIL threshold.
   These types of tasks are most likely to cause user visible jank.
   Lower blocking thresholds are also used for shorter periods of time,
   so shorter tasks are not likely to be deferred for a long time
   in any case.

3. Also mention network tasks in the log message.

BUG=613230
==========

to

==========
scheduler: Avoid false alerts about expensive task blocking

This patch adjusts the logic for logging a console message when an
expensive task is blocked:

1. Don't log messages when all timer tasks are blocked (e.g., while
   waiting for a touchstart response). There's nothing the developer can
   do to avoid this type of blocking.

2. Only report blocking for tasks which exceed the 50ms RAIL threshold.
   These types of tasks are most likely to cause user visible jank.
   Lower blocking thresholds are also used for shorter periods of time,
   so shorter tasks are not likely to be deferred for a long time
   in any case.

3. Also mention network tasks in the log message.

BUG=613230

Committed: https://crrev.com/c66723959e9a37f1a5bbd821366a2ee24a9537c2
Cr-Commit-Position: refs/heads/master@{#396467}
==========

[commit-bot: I haz the power, 2016-05-27 14:53:06]

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