Update wgpu to c2e0ad293 (2024-09-12)
Categories
(Core :: Graphics: WebGPU, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox132 | --- | fixed |
People
(Reporter: jimb, Assigned: jimb)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
What it says on the tin.
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 1•2 months ago
|
||
Assignee | ||
Comment 2•2 months ago
|
||
Updated•2 months ago
|
Assignee | ||
Comment 3•2 months ago
|
||
Assignee | ||
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 5•2 months ago
|
||
Comment 6•2 months ago
|
||
Implemented with moz-webgpu-cts
v1.3.0, using moz-webgpu-cts update-expected --preset reset-contradictory --implementation-status backlog
with reports from try:c75bc73e5301.
Updated•2 months ago
|
Updated•2 months ago
|
Comment 7•2 months ago
|
||
Try push with the latest patch stack that includes adjustments to CTS metadata: try:da341fe84de4
Short summary: Looking good! 😀 For example, all regressions in D221366 have been undone.
Comment 10•2 months ago
|
||
bugherder |
Comment 11•2 months ago
|
||
Backed out 4 changesets (bug 1917102) for causing crashes (bug 1917444).
Comment 12•2 months ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/50016ed27344
Comment 13•2 months ago
|
||
The crashes in Bug 1917444 are caused by us now using into_device_result
on the result of D3D12CreateDevice
(https://github.com/gfx-rs/wgpu/commit/dd01b6d20967f1b4a74e9a75baec6b54545ebfec) which panics on unexpected error variants due to the internal_error_panic
feature being turned on.
Comment 14•2 months ago
|
||
I put up https://github.com/gfx-rs/wgpu/pull/6241 to fix this.
Updated•2 months ago
|
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 15•2 months ago
|
||
Assignee | ||
Comment 16•2 months ago
|
||
That push didn't work out; apparently there are keys that are rotated that are stored both in the CI infra code and in Mozilla Central, so if you do a try push with old sources, you get errors like:
Loading initial page https://web-platform.test:8443/testharness_runner.html failed. Ensure that the there are no other programs bound to this port and that your firewall rules or network setup does not prevent access.
If I'm understanding this comment, the fix is to rebase on something more recent. Hence:
New try push
Assignee | ||
Comment 17•2 months ago
|
||
Okay, that try push looks good.
Updated•2 months ago
|
Comment 18•2 months ago
|
||
Comment 19•2 months ago
|
||
bugherder |
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Description
•