[coverage] Use optimized builds for coverage data.

[coverage] Use optimized builds for coverage data.

Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
NOTRY=true

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

[Michael Achenbach, 2016-02-22 14:19:48]

Description was changed from

==========
[coverage] Use optimized builds for coverage data.

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

to

==========
[coverage] Use optimized builds for coverage data.

Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented
in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in
B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
==========

[Michael Achenbach, 2016-02-22 14:19:49]

machenbach@chromium.org changed reviewers:
+ jkummerow@chromium.org, tandrii@chromium.org

[Michael Achenbach, 2016-02-22 14:20:05]

PTAL

[Michael Achenbach, 2016-02-22 14:20:16]

Description was changed from

==========
[coverage] Use optimized builds for coverage data.

Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented
in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in
B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
==========

to

==========
[coverage] Use optimized builds for coverage data.

Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented
in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in
B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
NOTRY=true
==========

[tandrii(chromium), 2016-02-22 14:29:51]

lgtm

[Michael Achenbach, 2016-02-22 14:36:58]

The CQ bit was checked by machenbach@chromium.org

[commit-bot: I haz the power, 2016-02-22 14:37:10]

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

[commit-bot: I haz the power, 2016-02-22 14:38:31]

Description was changed from

==========
[coverage] Use optimized builds for coverage data.

Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented
in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in
B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
NOTRY=true
==========

to

==========
[coverage] Use optimized builds for coverage data.

Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented
in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in
B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
NOTRY=true
==========

[commit-bot: I haz the power, 2016-02-22 14:38:31]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-22 14:39:14]

Description was changed from

==========
[coverage] Use optimized builds for coverage data.

Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented
in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in
B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
NOTRY=true
==========

to

==========
[coverage] Use optimized builds for coverage data.

Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented
in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in
B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
NOTRY=true

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

[commit-bot: I haz the power, 2016-02-22 14:39:15]

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