Automatically adding ccs based on suspected regression changelists:

[interpreter] Add bytecode for leading array spreads. by dhai@google.com - https://chromium.googlesource.com/v8/v8/+/1c48d52bb1ee9bb28e146c60eda08cd4afaa5745

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

This CL has somehow closed a bunch of existing issues, but opened some new ones. Maybe those new ones are the same as the closed ones with changed symptoms? Or the new symptoms mask the old ones.

I'll dupe the other bugs on this one.

 Issue 879316  has been merged into this issue.

 Issue 879427  has been merged into this issue.

 Issue 879430  has been merged into this issue.

 Not sure which issues it would have closed, or why. Anyways, the CL was reverted a few mins ago.

For the record, the CL closed https://bugs.chromium.org/p/chromium/issues/detail?id=788139, which is about inconsistent error messages.

ClusterFuzz has detected this issue as fixed in range 55543:55544.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,slow_path
  sources: 346
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=55519:55520
Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=55543:55544

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

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 5743168994410496 is verified as fixed, so closing issue as verified.

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