Update wgpu to upstream 64394cc7 (2026-5-6)
Categories
(Core :: Graphics: WebGPU, task, P1)
Tracking
()
People
(Reporter: jimb, Assigned: jimb, NeedInfo)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
What it says on the tin.
| Assignee | ||
Comment 1•6 days ago
|
||
Updated•6 days ago
|
| Assignee | ||
Updated•6 days ago
|
| Assignee | ||
Updated•6 days ago
|
| Assignee | ||
Updated•6 days ago
|
| Assignee | ||
Updated•6 days ago
|
Updated•6 days ago
|
| Assignee | ||
Comment 2•6 days ago
|
||
| Assignee | ||
Comment 3•5 days ago
|
||
There's a regression in buffer mapping. Stack:
#23 wgpu_bindings::server::process_buffer_map::{async_block#0} () at gfx/wgpu_bindings/src/server.rs:2613
#24 async_task::runnable::spawn_local::{impl#1}::poll<wgpu_bindings::server::process_buffer_map::{async_block_env#0}> (self=..., cx=<optimized out>) at third_party/rust/async-task/src/runnable.rs:132
#25 0x00007f49fb7993b3 in async_task::raw::RawTask<async_task::runnable::spawn_local::Checked<wgpu_bindings::server::process_buffer_map::{async_block_env#0}>, (), moz_task::executor::{impl#6}::spawn_local::{closure_env#0}<wgpu_bindings::server::process_buffer_map::{async_block_env#0}>>::run<async_task::runnable::spawn_local::Checked<wgpu_bindings::server::process_buffer_map::{async_block_env#0}>, (), moz_task::executor::{impl#6}::spawn_local::{closure_env#0}<wgpu_bindings::server::process_buffer_map::{async_block_env#0}>> (ptr=0x7f49a87fb400)
at third_party/rust/async-task/src/raw.rs:511
| Assignee | ||
Comment 4•5 days ago
|
||
There seem to be several other regressions as well on Mac and Windows.
| Assignee | ||
Comment 5•5 days ago
|
||
(In reply to Jim Blandy :jimb from comment #3)
There's a regression in buffer mapping.
I think wgpu#9513 will fix this one.
Updated•5 days ago
|
| Assignee | ||
Comment 6•5 days ago
|
||
| Assignee | ||
Comment 7•4 days ago
|
||
This cleans up a ton of failures in api/operation/buffers/map.
| Assignee | ||
Comment 8•4 days ago
|
||
Lots of new passes in bitcast and shader/validation/shader_io/interpolate as well.
| Assignee | ||
Updated•4 days ago
|
| Assignee | ||
Comment 9•4 days ago
|
||
The Mac regressions seem to be timeout-related. I don't think there's anything we should do about those until bug 1870699 is landed.
Updated•4 days ago
|
| Assignee | ||
Comment 10•3 days ago
|
||
Okay, finally the tests are all finished running.
| Assignee | ||
Comment 11•2 days ago
|
||
Lando was down for a bit, and now it seems like there are conflicts in the test expectations, so this needs a rebase on a newer autoland.
Comment 12•2 days ago
|
||
Comment 13•2 days ago
|
||
Comment 14•2 days ago
|
||
| Assignee | ||
Comment 16•1 day ago
•
|
||
This is odd. It's a formatting issue? I only used cargo vet for this...
json /builds/worker/issues.json --vcs-diff /builds/worker/vcs-diff.diff
Updating git repository `https://github.com/glandium/allocator-api2`
...
Locking 0 packages to latest compatible versions
note: pass `--verbose` to see 278 unchanged dependencies behind latest
[INFO] Using /builds/worker/checkouts/gecko/.cargo/config.toml.
Vet error: Your cargo-vet store (supply-chain) has consistency errors
related error: A file in the store is not correctly formatted:
--- old/imports.lock
+++ new/imports.lock
@@ -294,18 +294,18 @@
user-id = 55123
user-login = "rust-lang-owner"
+[[publisher.hashbrown]]
+version = "0.17.0"
+when = "2026-04-09"
+user-id = 55123
+user-login = "rust-lang-owner"
+
[[publisher.hawk]]
version = "5.0.1"
when = "2024-09-13"
user-id = 158511
user-login = "lotas"
user-name = "Yarik"
-
-[[publisher.hashbrown]]
-version = "0.17.0"
-when = "2026-04-09"
-user-id = 55123
-user-login = "rust-lang-owner"
[[publisher.headers]]
version = "0.3.9"
Run `./mach cargo vet` for more information.
| Assignee | ||
Comment 17•1 day ago
|
||
Ran mach cargo vet fmt, it made the change reported above; amended that into the patch, tried landing again.
Comment 18•1 day ago
|
||
Comment 19•23 hours ago
|
||
| bugherder | ||
Comment 20•14 hours ago
|
||
Comment 21•14 hours ago
|
||
Backed out for causing multiple webgpu failures
Backout link
Push with failures
Failure log(s)
Failure log(s)
Failure log(s)
Comment 22•11 hours ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/00019f67436f
Description
•