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

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

Assigning to SwiftShader team for more updates.

@capn - Could you please look into this issue?

Thanks! 

 Issue 797247  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 529739:529747.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  ppparse
  pp::ExpressionParser::parse
  pp::DirectiveParser::parseExpressionIf
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=521492:521536
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=529739:529747

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

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

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