Regression range points to 6d42c4504a2522e235975a0189c0bd90b6fde47f.

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

commit 647d7b6c33e8cc37e3c189c717eeab8566e6a656
Author: rmcilroy <rmcilroy@chromium.org>
Date: Thu Jan 26 10:27:40 2017

[Compiler] Put background compilation of eager inner functions behind a flag.

Disabled until clusterfuzz issues are sorted.

BUG= v8:5203 ,  v8:5215 ,  chromium:685515 ,  chromium:685476 

Review-Url: https://codereview.chromium.org/2658803002
Cr-Commit-Position: refs/heads/master@{#42686}

[modify] https://crrev.com/647d7b6c33e8cc37e3c189c717eeab8566e6a656/src/compiler.cc
[modify] https://crrev.com/647d7b6c33e8cc37e3c189c717eeab8566e6a656/src/flag-definitions.h

ClusterFuzz has detected this issue as fixed in range 42685:42686.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6203649358561280

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_ignition_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  compile_job_->can_execute_on_background_thread() in compiler-dispatcher-job.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 42666:42667
Fixed: V8: 42685:42686

Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94QSKv7VEqULopXyB12xCtM42iOWMQzOGigWx3KRn-uh9RbNdnIhzLd7Hi73Q-ONjv7uosjrABNb-bI2vpem0zlkz0iEzcTL0_6w_0MCmARCMPDQM7kf6Lu-oMR6nHUeYSBhoEia6jHiQxYwDfxW73MQXjY3tW-YsaqZMwvgyG8SldIL1idJAfofLhRgLzF2vMoOr0S7r-tFO5LZohOf65ZWnkYgimreLW8MjpOB2cgPXTtXGzCG6mzeL97etwo9B33g1GN1kMrR38DBADn-aocD3x8gmTFcGR1cu_P34lZ7Ahyp9Bt3xvwoxC-sOttJUJWnBTA2TSM_6NFKbrRMLmcYUfjQW85mils7ewTq9VH797x2zo?testcase_id=6203649358561280

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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

Just put behind a flag. Adding flag to make sure we don't loose the report.

Not sure why this didn't get posted on the bug, but fixed in https://chromium-review.googlesource.com/c/441047/

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.