fix pathops fuzz bugs

fix pathops fuzz bugs

Fail out in a couple of new places when the input data is very
large and exceeds the limits of the pathops machinery.

Most of the change here plumbs in a way to exclude an assert in
one of these exceptional cases. The current SkAddIntersection
implementation and the inner functions it calls has no way to
report an error to the root caller for an early exit, so rather
than add that in, exclude the assert when the test that would
trigger it runs (allowing the test to otherwise ensure that it
properly fails).

TBR=reed@google.com
BUG=617586, 617635
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2046713003

Committed: https://skia.googlesource.com/skia/+/dae6b97705fde08958b1a36fa6ce685d28fc692c

[caryclark, 2016-06-07 15:32:28]

Description was changed from

==========
looking for fails in all the wrong places

Running Chrome with the output of three different fuzzers fail
but capturing the input data to pathops isolated in the contained
tests did not fail locally.

Hopefully running these tests through a set of bots will
reproduce the failure.

TBR=reed@google.com
BUG=617586,617635
==========

to

==========
looking for fails in all the wrong places

Running Chrome with the output of three different fuzzers fail
but capturing the input data to pathops isolated in the contained
tests did not fail locally.

Hopefully running these tests through a set of bots will
reproduce the failure.

TBR=reed@google.com
BUG=617586,617635
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2046713003
==========

[caryclark, 2016-06-07 20:06:43]

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

[caryclark, 2016-06-07 20:10:52]

Description was changed from

==========
looking for fails in all the wrong places

Running Chrome with the output of three different fuzzers fail
but capturing the input data to pathops isolated in the contained
tests did not fail locally.

Hopefully running these tests through a set of bots will
reproduce the failure.

TBR=reed@google.com
BUG=617586,617635
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2046713003
==========

to

==========
fix pathops fuzz bugs

Fail out in a couple of new places when the input data is very
large and exceeds the limits of the pathops machinery.

Most of the change here plumbs in a way to exclude an assert in
one of these exceptional cases. The current SkAddIntersection
implementation and the inner functions it calls has no way to
report an error to the root caller for an early exit, so rather
than add that in, exclude the assert when the test that would
trigger it runs (allowing the test to otherwise ensure that it
properly fails).

TBR=reed@google.com
BUG=617586,617635
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2046713003
==========

[rmistry, 2016-06-07 20:24:37]

The CQ bit was unchecked by rmistry@google.com

[rmistry, 2016-06-07 20:24:53]

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

[commit-bot: I haz the power, 2016-06-07 20:31:50]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2046713003/100001

[commit-bot: I haz the power, 2016-06-07 21:22:33]

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

[commit-bot: I haz the power, 2016-06-07 21:22:34]

Dry run: This issue passed the CQ dry run.

[caryclark, 2016-06-08 11:27:17]

The CQ bit was checked by caryclark@google.com

[commit-bot: I haz the power, 2016-06-08 11:27:22]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2046713003/100001

[commit-bot: I haz the power, 2016-06-08 11:28:23]

Description was changed from

==========
fix pathops fuzz bugs

Fail out in a couple of new places when the input data is very
large and exceeds the limits of the pathops machinery.

Most of the change here plumbs in a way to exclude an assert in
one of these exceptional cases. The current SkAddIntersection
implementation and the inner functions it calls has no way to
report an error to the root caller for an early exit, so rather
than add that in, exclude the assert when the test that would
trigger it runs (allowing the test to otherwise ensure that it
properly fails).

TBR=reed@google.com
BUG=617586,617635
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2046713003
==========

to

==========
fix pathops fuzz bugs

Fail out in a couple of new places when the input data is very
large and exceeds the limits of the pathops machinery.

Most of the change here plumbs in a way to exclude an assert in
one of these exceptional cases. The current SkAddIntersection
implementation and the inner functions it calls has no way to
report an error to the root caller for an early exit, so rather
than add that in, exclude the assert when the test that would
trigger it runs (allowing the test to otherwise ensure that it
properly fails).

TBR=reed@google.com
BUG=617586,617635
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2046713003

Committed:
https://skia.googlesource.com/skia/+/dae6b97705fde08958b1a36fa6ce685d28fc692c
==========

[commit-bot: I haz the power, 2016-06-08 11:28:24]

Committed patchset #6 (id:100001) as
https://skia.googlesource.com/skia/+/dae6b97705fde08958b1a36fa6ce685d28fc692c