Add Progressive JPEG YUV decoding layout tests

Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
cause the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

TBR=scroggo@chromium.org
BUG=598549
Committed: https://crrev.com/dca359146de5ca000b3e6681b91a468435b4f4b7
Cr-Commit-Position: refs/heads/master@{#384874}

[Noel Gordon, 2016-04-01 05:51:03]

Description was changed from

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
exhibit the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

BUG=598549
==========

to

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
exhibit the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

BUG=598549
==========

[Noel Gordon, 2016-04-01 05:51:03]

noel@chromium.org changed reviewers:
+ scroggo@chromium.org

[Noel Gordon, 2016-04-01 06:49:57]

The CQ bit was checked by noel@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-01 06:50:23]

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

[commit-bot: I haz the power, 2016-04-01 07:24:49]

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

[commit-bot: I haz the power, 2016-04-01 07:24:50]

Dry run: Try jobs failed on following builders:
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[Noel Gordon, 2016-04-01 22:15:37]

The CQ bit was checked by noel@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-01 22:16:36]

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

[Noel Gordon, 2016-04-01 23:19:44]

Description was changed from

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
exhibit the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

BUG=598549
==========

to

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
cause the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

BUG=598549
==========

[commit-bot: I haz the power, 2016-04-02 00:26:59]

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

[commit-bot: I haz the power, 2016-04-02 00:26:59]

Dry run: This issue passed the CQ dry run.

[Noel Gordon, 2016-04-04 05:38:45]

The CQ bit was checked by noel@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-04 05:38:58]

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

[Noel Gordon, 2016-04-04 06:31:45]

The CQ bit was checked by noel@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-04 06:31:52]

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

[commit-bot: I haz the power, 2016-04-04 07:42:55]

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

[commit-bot: I haz the power, 2016-04-04 07:42:56]

Dry run: This issue passed the CQ dry run.

[Noel Gordon, 2016-04-04 08:39:56]

Finally, all test passing!  Leon, I will land this now, but please review when
you have time ...

[Noel Gordon, 2016-04-04 08:40:05]

The CQ bit was checked by noel@chromium.org

[commit-bot: I haz the power, 2016-04-04 08:40:19]

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

[commit-bot: I haz the power, 2016-04-04 08:40:20]

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

[commit-bot: I haz the power, 2016-04-04 08:40:21]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Noel Gordon, 2016-04-04 09:49:55]

Description was changed from

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
cause the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

BUG=598549
==========

to

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
cause the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

TBR=scroggo@chromium.org
BUG=598549
==========

[Noel Gordon, 2016-04-04 09:50:19]

On 2016/04/04 08:40:21, commit-bot: I haz the power wrote:
> No L-G-T-M from a valid reviewer yet. 
> CQ run can only be started by full committers or once the patch has
> received an L-G-T-M from a full committer.
> Even if an L-G-T-M may have been provided, it was from a non-committer,
> _not_ a full super star committer.
> See http://www.chromium.org/getting-involved/become-a-committer
> Note that this has nothing to do with OWNERS files.

Me forgets the TBR line :)

[Noel Gordon, 2016-04-04 09:50:25]

The CQ bit was checked by noel@chromium.org

[commit-bot: I haz the power, 2016-04-04 09:50:38]

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

[commit-bot: I haz the power, 2016-04-04 09:55:44]

Description was changed from

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
cause the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

TBR=scroggo@chromium.org
BUG=598549
==========

to

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
cause the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

TBR=scroggo@chromium.org
BUG=598549
==========

[commit-bot: I haz the power, 2016-04-04 09:55:45]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2016-04-04 09:56:59]

Description was changed from

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
cause the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

TBR=scroggo@chromium.org
BUG=598549
==========

to

==========
Add Progressive JPEG YUV decoding layout tests

See also issue 597127. Use a <meta> viewport tag to force
GPU rasterization on the Android bots where supported and
add test cases for images and for the <canvas> element:

  fast/images/jpeg-yuv-progressive-image.html
  fast/images/jpeg-yuv-progressive-canvas.html

Add new Progressive JPEG image resources: they were built
using the ImageMagik

  % convert -size <size> plasma:fractal -paint

command. Details of the JPEG image encodings are:

ycbcr-progressive-000.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	200 × 200
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-001.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	250 × 250
Y Cb Cr Sub Sampling	YCbCr 4:4:4 (1 1)

ycbcr-progressive-002.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	300 × 300
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

ycbcr-progressive-003.jpg

Progressive DCT, Huffman coding
Bits Per Sample	8
Color Components	3
Image Size	350 × 350
Y Cb Cr Sub Sampling	YCbCr 4:2:0 (2 2)

Note: the progressive images with YUV 4:2:0 encoding both
cause the bug reported in issue 597127.

The new tests added in this CL provide some test coverage
for issue 597127 (run with --force-gpu-rasterization) but
more work is needed to automate that on the bots, such as
with a virtual test suite for this flag (it has none).

TBR=scroggo@chromium.org
BUG=598549

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

[commit-bot: I haz the power, 2016-04-04 09:57:00]

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

[msarett, 2016-04-04 13:55:15]

msarett@google.com changed reviewers:
+ msarett@google.com

[msarett, 2016-04-04 13:55:16]

lgtm

[scroggo_chromium, 2016-04-04 19:15:03]

lgtm