Closed
Bug 1950796
Opened 24 days ago
Closed 19 days ago
Regression on WASM-Godot-WASM-instantiate for Firefox (Tiering) and wasm-baseline around 10Feb2025
Categories
(Core :: JavaScript: WebAssembly, defect)
Core
JavaScript: WebAssembly
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox136 | --- | unaffected |
firefox137 | --- | fixed |
People
(Reporter: mayankleoboy1, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Trend of increase in time around 10Feb-11Feb.
Reporter | ||
Comment 1•24 days ago
|
||
There may be more than 1 regression here. Difficult top say as the test is run on mozilla-central so not sure how to do backfills.
Comment 2•19 days ago
|
||
This is going to be caused by bug 1943696, which regressed our baseline compilation speed for nightly-only due to some new profiling instrumentation. Bug 1949824 partially addressed the regression. The rest of the regression I think we should just take because it's nightly only.
Status: NEW → RESOLVED
Closed: 19 days ago
Resolution: --- → FIXED
Reporter | ||
Updated•19 days ago
|
Comment 3•19 days ago
|
||
Set release status flags based on info from the regressing bug 1943696
status-firefox136:
--- → unaffected
status-firefox137:
--- → affected
status-firefox138:
--- → affected
status-firefox-esr128:
--- → unaffected
Updated•17 days ago
|
status-firefox138:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•