Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/b0d0d57d2b43cb3af2b0b41e0a3457d1e8ef2b1c ([date] Date parser says true even for wrong dates, check twice.).

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.

At a glance I'm guessing this probably isn't a security issue. Feel free to remove the security labels and set this to Type-Bug if that's the case, or let me know and I can.

This is definitely not a security issue.

ClusterFuzz has detected this issue as fixed in range 57861:57862.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  save_days == DaysFromYearMonth(*year, 0) + days in date.cc
  v8::internal::DateCache::YearMonthDayFromDays
  v8::internal::DateCache::EquivalentTime
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=33148:33149
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=57861:57862

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

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

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