Closed
Bug 1947403
Opened 1 month ago
Closed 1 month ago
TypeError: can't access property "intent", suggestion is null
Categories
(Core :: Machine Learning, defect)
Core
Machine Learning
Tracking
()
RESOLVED
FIXED
137 Branch
Tracking | Status | |
---|---|---|
firefox137 | --- | fixed |
People
(Reporter: tarek, Assigned: cgopal)
References
Details
(Whiteboard: [genai])
Attachments
(1 file)
Running the suggest perf test I get an error
$ MOZ_FETCHES_DIR=/Users/tarekziade/Dev/fetches ./mach perftest toolkit/components/ml/tests/browser/browser_ml_suggest_inference.js --hooks toolkit/components/ml/tests/tools/hooks_local_hub.py --mochitest-extra-args headless
FAIL Uncaught exception in test bound test_ml_generic_pipeline - at chrome://mochitests/content/browser/toolkit/components/ml/tests/browser/browser_ml_suggest_inference.js:131 - TypeError: can't access property "intent", suggestion is null
I also noticed in the code that all errors are silently captured by MLSuggest making it a bit hard to spot the issue
We should avoid this design and capture at least in the logs unintended behaviors - e.g. a suggest feature not ready is different from a feature that runs and fails.
Reporter | ||
Updated•1 month ago
|
Assignee: nobody → cgopal
Updated•1 month ago
|
Updated•1 month ago
|
Attachment #9465538 -
Attachment description: WIP: Bug 1947403 - ml_suggest_inference changed to serial asyncs → Bug 1947403 - ml_suggest_inference changed to serial asyncs r?tarek
Thanks @tarek!
The problem was around the batching of test inference data. I tested the fix locally now
MOZ_FETCHES_DIR=/Users/cgopal/work/perf-models ./mach perftest toolkit/components/ml/tests/browser/browser_ml_suggest_inference.js --hooks toolkit/components/ml/tests/tools/hooks_local_hub.py --mochitest-extra-args headless
Please find the changes in https://phabricator.services.mozilla.com/D237799
Pushed by cgopal@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2969bc17af29
ml_suggest_inference changed to serial asyncs r=tarek
Status: NEW → RESOLVED
Closed: 1 month ago
status-firefox137:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•