[fuzz] Fix concurrency issue when fuzzer fails in -check The existing concurrent code in -check does not correctly handle when a gorountine returns failure. Specifically it doesn't wait for the other goroutines to finish their current task and stop before tearing down the progress bar, thus there is a race that sometimes leads to instead of outputting the error text of the failing run will cause a Go panic due to trying to send on a channel that is closed. In this CL I am removing the non-idiomatic concurrency code and replacing it with usage of the standard libraries and extensions for handling this case. Since this was the only usage of RunConcurrent, and it is error prone, I am also removing it. Fixes: 561685245 Change-Id: Ib2ec8a2ce09180d42b1cccabf866ed803d37b56b Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/342195 Commit-Queue: dan sinclair <dsinclair@chromium.org> Auto-Submit: Ryan Harrison <rharrison@chromium.org> Reviewed-by: dan sinclair <dsinclair@chromium.org>
Dawn is an open-source and cross-platform implementation of the WebGPU standard. More precisely it implements webgpu.h that is a one-to-one mapping with the WebGPU IDL. Dawn is meant to be integrated as part of a larger system and is the underlying implementation of WebGPU in Chromium.
Dawn provides several WebGPU building blocks:
webgpu.h version that Dawn implements.webgpu.h.Helpful links:
Developer documentation:
User documentation: (TODO, figure out what overlaps with the webgpu.h docs)
BSD 3-Clause License, please see LICENSE.
This is not an officially supported Google product.