Open
Bug 1951856
Opened 13 days ago
Updated 10 hours ago
Some of the browser-ml-smart-tab-perf tests now show "0 chars/s"
Categories
(Core :: Machine Learning, defect, P3)
Core
Machine Learning
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox-esr128 | --- | unaffected |
| firefox136 | --- | wontfix |
| firefox137 | --- | wontfix |
| firefox138 | --- | affected |
People
(Reporter: mayankleoboy1, Unassigned)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fxp])
Flags: needinfo?(vbaungally)
|
Reporter | |
Updated•13 days ago
|
Summary: Some of the browser-ml-smart=tab-per tests now show "0 chars/s" → Some of the browser-ml-smart-tab-perf tests now show "0 chars/s"
|
|
Reporter | |
Comment 1•13 days ago
|
||
Related perf-alert : https://treeherder.mozilla.org/perfherder/alerts?id=44185&hideDwnToInv=0
|
||
Comment 3•13 days ago
|
||
Set release status flags based on info from the regressing bug 1950466
status-firefox136:
--- → unaffected
status-firefox137:
--- → affected
status-firefox138:
--- → affected
status-firefox-esr128:
--- → unaffected
|
||
Updated•11 days ago
|
Severity: -- → S3
Priority: -- → P3
|
|
||
Updated•11 days ago
|
Whiteboard: [fxp]
|
||
Updated•11 days ago
|
|
||
Comment 4•9 days ago
|
||
Also commented in this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1952191.
The latest running model (v0.3.4) doesn't give the characterSpeed metric info when running. This is ok since we don't use those. It's better to know the memory and latency metrics (which we do use) and have that be the one that matches the production one.
Flags: needinfo?(vbaungally)
|
||
Comment 5•6 days ago
|
||
Per the above this seems test-only.
|
||
Updated•10 hours ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•