Dirty mipmaps whenever we upload new contents for a texture.

Dirty mipmaps whenever we upload new contents for a texture.

Found a bug where we rendered with two identically sized textures. On
the first frame, everything worked. On subsequent frames, we would get
the other texture from the cache, causing us to inherit the mips from
the wrong texture.

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1836143003

Committed: https://skia.googlesource.com/skia/+/3ebd2760dd34da6f5af23e9c7cb1b6a61e9cea9d

[Brian Osman, 2016-03-29 14:19:41]

Description was changed from

==========
Dirty mipmaps whenever we upload new contents for a texture.

Found a bug where we rendered with two identically sized textures. On
the first frame, everything worked. On subsequent frames, we would get
the other texture from the cache, causing us to inherit the mips from
the wrong texture.

BUG=skia:
==========

to

==========
Dirty mipmaps whenever we upload new contents for a texture.

Found a bug where we rendered with two identically sized textures. On
the first frame, everything worked. On subsequent frames, we would get
the other texture from the cache, causing us to inherit the mips from
the wrong texture.

BUG=skia:
GOLD_TRYBOT_URL=
https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&is...
==========

[Brian Osman, 2016-03-29 14:21:14]

brianosman@google.com changed reviewers:
+ bsalomon@google.com

[Brian Osman, 2016-03-29 14:21:23]

The CQ bit was checked by brianosman@google.com to run a CQ dry run

[commit-bot: I haz the power, 2016-03-29 14:21:37]

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

[commit-bot: I haz the power, 2016-03-29 14:31:36]

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

[commit-bot: I haz the power, 2016-03-29 14:31:37]

Dry run: This issue passed the CQ dry run.

[Brian Osman, 2016-03-29 17:15:03]

Does this look okay?

[bsalomon, 2016-03-29 18:16:42]

On 2016/03/29 17:15:03, Brian Osman wrote:
> Does this look okay?

lgtm, sorry forgot to take a look earlier!

[Brian Osman, 2016-03-29 18:26:17]

The CQ bit was checked by brianosman@google.com

[commit-bot: I haz the power, 2016-03-29 18:26:25]

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

[commit-bot: I haz the power, 2016-03-29 18:27:24]

Description was changed from

==========
Dirty mipmaps whenever we upload new contents for a texture.

Found a bug where we rendered with two identically sized textures. On
the first frame, everything worked. On subsequent frames, we would get
the other texture from the cache, causing us to inherit the mips from
the wrong texture.

BUG=skia:
GOLD_TRYBOT_URL=
https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&is...
==========

to

==========
Dirty mipmaps whenever we upload new contents for a texture.

Found a bug where we rendered with two identically sized textures. On
the first frame, everything worked. On subsequent frames, we would get
the other texture from the cache, causing us to inherit the mips from
the wrong texture.

BUG=skia:
GOLD_TRYBOT_URL=
https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&is...

Committed:
https://skia.googlesource.com/skia/+/3ebd2760dd34da6f5af23e9c7cb1b6a61e9cea9d
==========

[commit-bot: I haz the power, 2016-03-29 18:27:25]

Committed patchset #1 (id:1) as
https://skia.googlesource.com/skia/+/3ebd2760dd34da6f5af23e9c7cb1b6a61e9cea9d