Google Git
Sign in
dawn / dawn / a45458024121d4cd6c7098d8af067746fa46f40b
commita45458024121d4cd6c7098d8af067746fa46f40b[log] [tgz]
authorKai Ninomiya <kainino@chromium.org>Tue Apr 01 19:54:20 2025 -0700
committerDawn LUCI CQ <dawn-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 01 19:54:20 2025 -0700
tree7d4880664386e40da1c93c8df4e1c6f23621c958
parent86755d629314f9f9d12c4c356e478d6f251e398c [diff]
test_runner.js: fix heartbeat code disrupting async behavior

The way we injected heartbeats meant we were returning a userspace
promise to the CTS, rather than the real one from the browser.
Modify this so that we attach heartbeats to the promise, but still
return the original promise object. This fixes
`webgpu:api,validation,buffer,mapping:` tests that were testing the
exact behavior of the API (task vs. microtask).

There's a small chance this will fix some other tests, too.

I've removed the code that was supposed to trigger a heartbeat both
before and after the responding code. It would not have worked:
resolve() doesn't run the awaiting code, it just marks the promise as
resolved, so both heartbeats ran before. I tried fixing it, but it made
some tests very slow, so I've just removed the second heartbeat. I don't
think it's that useful; it only helps on slow synchronous code.

Fixed: 42241427
Change-Id: I4995c3518f1dc5d05524a0155f601f9103891d8d
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/233954
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Auto-Submit: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: dan sinclair <dsinclair@chromium.org>
3 files changed
tree: 7d4880664386e40da1c93c8df4e1c6f23621c958
  1. .github/
  2. .vscode/
  3. build_overrides/
  4. docs/
  5. generator/
  6. include/
  7. infra/
  8. scripts/
  9. src/
  10. test/
  11. third_party/
  12. tools/
  13. webgpu-cts/
  14. build
  15. buildtools
  16. testing
  17. .bazelrc
  18. .clang-format
  19. .clang-tidy
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .gn
  25. AUTHORS
  26. BUILD.bazel
  27. BUILD.gn
  28. CMakeLists.txt
  29. CMakeSettings.json
  30. CODE_OF_CONDUCT.md
  31. codereview.settings
  32. CONTRIBUTING.md
  33. CPPLINT.cfg
  34. DEPS
  35. DIR_METADATA
  36. go.mod
  37. go.sum
  38. go_presubmit_support.py
  39. LICENSE
  40. OWNERS
  41. PRESUBMIT.py
  42. README.chromium
  43. README.md
  44. WATCHLISTS
  45. WORKSPACE.bazel
README.md

Build Status Matrix Space

Dawn, a WebGPU implementation

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 C/C++ headers that applications and other building blocks use.
    • The webgpu.h version that Dawn implements.
    • A C++ wrapper for the webgpu.h.
  • A “native” implementation of WebGPU using platforms' GPU APIs: D3D12, Metal, Vulkan and OpenGL. See per API support for more details.
  • A client-server implementation of WebGPU for applications that are in a sandbox without access to native drivers
  • Tint is a compiler for the WebGPU Shader Language (WGSL) that can be used in standalone to convert shaders from and to WGSL.

Helpful links:

Documentation table of content

Developer documentation:

User documentation: (TODO, figure out what overlaps with the webgpu.h docs)

License

BSD 3-Clause License, please see LICENSE.

Disclaimer

This is not an officially supported Google product.