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

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

ClusterFuzz has detected this issue as fixed in range 577867:577877.

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

Fuzzer: libFuzzer_sequence_manager_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  base::time_internal::TimeBase<base::TimeTicks>::operator-
  base::sequence_manager::internal::ThreadControllerImpl::SetNextDelayedDoWork
  base::sequence_manager::TimeDomain::SetNextWakeUpForQueue
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=576877:576893
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=577867:577877

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

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

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