Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/2e2860f74f9c610d5ffb3ee1778d937055d25dea ([ic] Introduce new IC for storing into array literals.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/c895a23a996beafcd706e18656c8673338167ebd

commit c895a23a996beafcd706e18656c8673338167ebd
Author: Georg Neis <neis@chromium.org>
Date: Mon Mar 05 10:09:01 2018

[ic] Relax a CHECK.

The CHECK didn't account for the recent introduction of
StoreInArrayLiteralIC.

Bug: v8:5940,  chromium:818438 
Change-Id: I73b4120eb39b16d766f0b1a9cb82ba44804b09a3
Reviewed-on: https://chromium-review.googlesource.com/947950
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Georg Neis <neis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#51719}
[modify] https://crrev.com/c895a23a996beafcd706e18656c8673338167ebd/src/feedback-vector.cc
[add] https://crrev.com/c895a23a996beafcd706e18656c8673338167ebd/test/mjsunit/regress/regress-818438.js

ClusterFuzz has detected this issue as fixed in range 51718:51719.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_cfi_d8
Platform Id: linux

Crash Type: Ill
Crash Address: 0x55ea61bf04c2
Crash State:
  v8::internal::FeedbackNexus::GetKeyedAccessStoreMode
  v8::internal::KeyedStoreIC::UpdateStoreElement
  v8::internal::StoreInArrayLiteralIC::Store
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=51708:51709
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=51718:51719

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

See https://github.com/google/clusterfuzz-tools 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 6269363175555072 is verified as fixed, so closing issue as verified.

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