cc: Don't always rebuild property trees in LayerImplTests

cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/3a011ab449665cc77c09c4032b75fce618bfa6d9
Cr-Commit-Position: refs/heads/master@{#403799}

[ajuma, 2016-07-05 14:08:16]

Description was changed from

==========
cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.
==========

to

==========
cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

[ajuma, 2016-07-05 15:27:50]

Description was changed from

==========
cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

to

==========
cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

[ajuma, 2016-07-05 15:27:50]

ajuma@chromium.org changed reviewers:
+ weiliangc@chromium.org

[ajuma, 2016-07-05 15:30:15]

I ran into this when working on tests for another CL (moving filters to the
effect tree).

[weiliangc, 2016-07-05 17:12:33]

The CQ bit was checked by weiliangc@chromium.org

[weiliangc, 2016-07-05 17:12:34]

lgtm

[commit-bot: I haz the power, 2016-07-05 17:12:41]

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-07-05 17:16:53]

Description was changed from

==========
cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

to

==========
cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

[commit-bot: I haz the power, 2016-07-05 17:16:54]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-05 17:16:59]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-05 17:18:04]

Description was changed from

==========
cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

to

==========
cc: Don't always rebuild property trees in LayerImplTests

Currently, the macros used for testing when draw properties need
updates always rebuild property trees. However, in cases where we
depend on information in property trees in order to decide whether
a draw property update is needed, rebuilding property trees can cause
us to test the wrong thing. This CL removes the automatic rebuilding
and makes callers responsible for rebuilding when needed.

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/3a011ab449665cc77c09c4032b75fce618bfa6d9
Cr-Commit-Position: refs/heads/master@{#403799}
==========

[commit-bot: I haz the power, 2016-07-05 17:18:05]

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