Non-functional code in queueEngineWarmup
Categories
(Firefox for Android :: General, defect)
Tracking
()
People
(Reporter: mstange, Assigned: mcarare)
References
(Regression)
Details
(Keywords: regression)
Attachments
(5 files)
I made a mistake in D277473 (from bug 2023004) which means that queueEngineWarmup is a no-op.
We already have a patch to fix it in D295868; I'm filing this bug to land it.
Comment 1•3 months ago
|
||
Set release status flags based on info from the regressing bug 2023004
Updated•3 months ago
|
| Assignee | ||
Comment 2•3 months ago
|
||
Key changes:
- Corrected the
queueEngineWarmupfunction signature by removing an extra set of braces that incorrectly wrapped therunOnVisualCompletenesscall.
Updated•3 months ago
|
Comment 5•3 months ago
|
||
Backed out for causing failures at openMultipleSelectedBookmarksInANewTabTest.
Backout link: https://hg.mozilla.org/integration/autoland/rev/bcac479b8b7d
Failure log: https://treeherder.mozilla.org/logviewer?job_id=570710804&repo=autoland&task=JkbG8ajFRhuFQUBgyqwfOA.0&lineNumber=326
Comment 6•3 months ago
•
|
||
A bit of a bizarre downstream effect (either unexpected or expected change now) is that this test uses a local server and the expected title we check for on tabs is different from before. The tab titles now appear as opposed to their previous full localhost URL. Perhaps related to engine warm-up and when that resolves?
In any case if that's expected now, this line just needs updating to reflect that if expected https://searchfox.org/firefox-main/source/mobile/android/fenix/app/src/androidTest/java/org/mozilla/fenix/ui/BookmarksTest.kt#181
Comment 7•3 months ago
|
||
Comment 8•3 months ago
|
||
| Assignee | ||
Comment 9•3 months ago
|
||
I would say the the page title is what is expected to be seen there, the URL would be just a fallback.
Comment 10•3 months ago
|
||
Comment 11•3 months ago
|
||
Thanks. For posterity: the stray braces on queueEngineWarmup made it return an uninvoked lambda instead of running its body, so engine.warmUp() never executed (w/o visual-completeness queue as intended).
Comment 12•3 months ago
|
||
| bugherder | ||
Comment 13•3 months ago
|
||
The patch landed in nightly and beta is affected.
:mcarare, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox152towontfix.
For more information, please visit BugBot documentation.
Comment 14•3 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: engine warm-up not triggered
- Code covered by automated testing?: no
- Fix verified in Nightly?: no
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: We are fixing a regression, putting things as they were before the patch that introduced the change.
- String changes made/needed?: No.
- Is Android affected?: yes
| Assignee | ||
Comment 15•3 months ago
|
||
Key changes:
- Corrected the
queueEngineWarmupfunction signature by removing an extra set of braces that incorrectly wrapped therunOnVisualCompletenesscall.
Original Revision: https://phabricator.services.mozilla.com/D295868
| Assignee | ||
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Comment 16•3 months ago
|
||
| uplift | ||
Comment 17•3 months ago
|
||
Verified as fixed on the latest Nightly 153.0a1 -from 08.06.2026 and Beta 152.0b9 with Lenovo Yoga Tab 11 (Android 12) and Samsung Galaxy S25( Android 15).
Updated•3 months ago
|
Description
•