Skip to content

Enable wgpu_validate_locks#9479

Draft
andyleiserson wants to merge 21 commits intogfx-rs:trunkfrom
andyleiserson:jj-push-srqw
Draft

Enable wgpu_validate_locks#9479
andyleiserson wants to merge 21 commits intogfx-rs:trunkfrom
andyleiserson:jj-push-srqw

Conversation

@andyleiserson
Copy link
Copy Markdown
Contributor

Connections
Link to the issues addressed by this PR, or dependent PRs in other repositories

When one pull request builds on another, please put "Depends on
#NNNN" towards the top of its description. This helps maintainers
notice that they shouldn't merge it until its ancestor has been
approved. Don't use draft PR status to indicate this.

Description
Describe what problem this is solving, and how it's solved.

Testing
Explain how this change is tested.

Squash or Rebase?

If your pull request contains multiple commits, please indicate whether
they need to be squashed into a single commit before they're merged,
or if they're ready to rebase onto trunk as they stand. In the
latter case, please ensure that each commit passes all CI tests, so
that we can continue to bisect along trunk to isolate bugs.

Checklist

  • I self-reviewed and fully understand this PR.
  • WebGPU implementations built with wgpu may be affected behaviorally.
  • Validation and feature gates are in place to confine behavioral changes.
  • Tests demonstrate the validation and altered logic works.
  • CHANGELOG.md entries for the user-facing effects of this change are present.
  • The PR is minimal, and doesn't make sense to land as multiple PRs.
  • Commits are logically scoped and individually reviewable.
  • The PR description has enough context to understand the motivation and solution implemented.

This does two things:

1. Installs a panicking device loss handler when running GPU tests.
2. Allows expect-failure cases looking for an "unexpected" driver
   error to match even when `internal_error_panic` is off.

Normally, `cargo xtask test` runs with `--all-features`, enabling
`internal_error_panic`, which always panics immediately on an
unexpected driver error. To avoid confusion if running tests
without that feature, also match such errors when the feature is
disabled and they manifest as device loss.
Fix a hypothetical race condition in `Device::maintain`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant