Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/92700bfccd1806971ab47773ebe95576a128a998 (Replace BlendState builder via BlendState descriptor.).

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.

Any clue about this bug, how can I reproduce this issue, @cwallez and @kainino?

This isn't related to your patch, I'll take this one.

ClusterFuzz has detected this issue as fixed in range 619888:619889.

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

Fuzzer: afl_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: dawn_wire_server_and_frontend_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  dawn_native::CommandAllocator::Allocate
  dawn_native::CommandBufferBuilder::PassEnded
  dawn_native::ProgrammablePassEncoder::EndPass
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=619011:619012
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=619888:619889

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

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

ClusterFuzz testcase 4807088739713024 is verified as fixed, so closing issue as verified.

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