Closed Bug 1859583 Opened 1 year ago Closed 1 year ago

[Easy Setup Feature] - Clean up test cases and unused logic

Categories

(Firefox :: Messaging System, task, P1)

task
Points:
5

Tracking

()

RESOLVED FIXED
122 Branch
Iteration:
122.1 - Nov 20 - Dec 1
Tracking Status
firefox122 --- fixed

People

(Reporter: nsauermann, Assigned: nsauermann, NeedInfo)

References

Details

(Whiteboard: [omc])

Attachments

(1 file)

With 1855031, easy setup screens will use targeting to render screens. Remove/refactor any used or redundant test cases (currently browser_aboutwelcome_multistage_mr.js and browser_aboutwelcome_screen_targeting.js test similar logic) as well as remove respective calls from AboutWelcomeParent and getAWContent

Summary: [Easy Setup Feature] - Clean up test cases → [Easy Setup Feature] - Clean up test cases and unused logic
Assignee: nobody → nsauermann
Status: NEW → ASSIGNED
Priority: -- → P1
Attachment #9360249 - Attachment description: WIP: Bug 1859583 - [Easy Setup Feature] - Clean up test cases and unused logic → Bug 1859583 - [Easy Setup Feature] - Clean up test cases and unused logic
Whiteboard: [omc]
Iteration: --- → 121.1 - Oct 23 - Nov 3
Attachment #9360249 - Attachment description: Bug 1859583 - [Easy Setup Feature] - Clean up test cases and unused logic → WIP: Bug 1859583 - [Easy Setup Feature] - Clean up test cases and unused logic
Attachment #9360249 - Attachment description: WIP: Bug 1859583 - [Easy Setup Feature] - Clean up test cases and unused logic → Bug 1859583 - [Easy Setup Feature] - Clean up test cases and unused logic
Pushed by nsauermann@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0bda9015bace [Easy Setup Feature] - Clean up test cases and unused logic r=omc-reviewers,pdahiya
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
Regressions: 1864194
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 121 Branch → ---
Severity: -- → S3
Iteration: 121.1 - Oct 23 - Nov 3 → 122.1 - Nov 20 - Dec 1
Points: --- → 3
Points: 3 → 5

I can see a regression in the load time on try with the reverted and base patch most evident when looking at welcome loadtime opt cold fission webrender:
original patch - 144.5ms
completely reverted try run - 70.1ms

Culprit seems to be the changes to removing ShellServices calls as this try run shows reduction in ms back to before values

Doing one more try run to confirm this with the ShellService calls reverted.

I'm not sure what the best way to proceed is since we no longer require those calls? NI'ing Ed/Punam for feedback.

Flags: needinfo?(pdahiya)
Flags: needinfo?(edilee)

It may have something to do with removing the lazy resource loading. You could try just statically importing ShellService at the top of AboutWelcomeParent (disabling the eslint warning for unused variables). It is going to get imported anyway by ASRouterTargeting, and is needed for the screen targeting expressions, but higher up in the stack. If the performance is not the same as the reverted try run, you could rule that out as a possibility.

(In reply to Shane Hughes [:aminomancer] from comment #6)

It may have something to do with removing the lazy resource loading. You could try just statically importing ShellService at the top of AboutWelcomeParent (disabling the eslint warning for unused variables). It is going to get imported anyway by ASRouterTargeting, and is needed for the screen targeting expressions, but higher up in the stack. If the performance is not the same as the reverted try run, you could rule that out as a possibility.

Oh that's smart, good call! Let me give that a shot. Thanks Shane

Maybe ShellService does some kind of value caching. The other point of interest in your patch is the removal of calls to ShellService for needPin/needDefault, these values are later used in the screen targeting expressions. I guess it's conceivable that the ESM calls early in startup previously caused ShellService to cache something, so it didn't need to be recomputed during the page load test when screen targeting was evaluated (saving ~75ms). So, you could try making dummy ShellService calls somewhere in AboutWelcomeParent, as you did with the static import.

Culprit seems to be the changes to removing ShellServices calls as this try run shows reduction in ms back to before values

As discussed , let's split the cleanup of test cases and shell service removal in their own respective patches to unblock this bug. Shell Service call removal can be done with fix of bug 1864194 proposing new baseline for load time and better highlight how ShellService API possible I/O interaction with an OS impacts welcome loadtime raptor test

Flags: needinfo?(pdahiya)
Attachment #9360249 - Attachment description: Bug 1859583 - [Easy Setup Feature] - Clean up test cases and unused logic → Bug 1859583 - [Easy Setup Feature] - Clean up test cases
Pushed by nsauermann@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/efe09552a4d3 [Easy Setup Feature] - Clean up test cases r=omc-reviewers,pdahiya
Status: REOPENED → RESOLVED
Closed: 1 year ago1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: