Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/320e66b0b6fe6b273e0d4773ffa32ede0e32db8c

commit 320e66b0b6fe6b273e0d4773ffa32ede0e32db8c
Author: Amin Hassani <ahassani@google.com>
Date: Sat Jun 02 00:44:52 2018

Marking 9999 ebuild for dev-util/puffin as stable.

Picking up these CLs:
- https://android-review.googlesource.com/c/platform/external/puffin/+/696969
- https://android-review.googlesource.com/c/platform/external/puffin/+/676722
- https://android-review.googlesource.com/c/platform/external/puffin/+/668216
- https://android-review.googlesource.com/c/platform/external/puffin/+/664942

BUG= chromium:848058 
TEST=unittests

Change-Id: Ic2681f78a01d3819961c0b2a960934909de5f8e4
Reviewed-on: https://chromium-review.googlesource.com/1081409
Commit-Ready: Amin Hassani <ahassani@chromium.org>
Tested-by: Amin Hassani <ahassani@chromium.org>
Reviewed-by: Nicolas Norvez <norvez@chromium.org>

[rename] https://crrev.com/320e66b0b6fe6b273e0d4773ffa32ede0e32db8c/dev-util/puffin/puffin-1.0.0-r421.ebuild

ClusterFuzz has detected this issue as fixed in range 2627580:2628014.

Detailed report: https://clusterfuzz.com/testcase?key=4667363467984896

Fuzzer: libFuzzer_chromeos_puffin_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  puffin_fuzzer
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=2627580:2628014

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4667363467984896

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 4667363467984896 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.