[Toolbar redesign] Remove toolbar redesign layout code.
Categories
(Firefox for Android :: Toolbar, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox140 | --- | fixed |
People
(Reporter: royang, Assigned: royang)
References
Details
(Keywords: perf-alert, Whiteboard: [fxdroid][group3])
Attachments
(1 file, 1 obsolete file)
In preparation to add toolbar redesign toolbar code to compose, remove related toolbar layout code.
Updated•11 months ago
|
| Assignee | ||
Comment 1•11 months ago
|
||
The plan here is to remove anything that allows the user to enable toolbar redesign since we are re-implementing that in compose.
| Assignee | ||
Comment 2•11 months ago
|
||
Updated•11 months ago
|
Backed out for causing fenix opt failures in BrowserJourneyBaselineProfileGenerator
| Assignee | ||
Comment 6•11 months ago
•
|
||
(In reply to amarc from comment #5)
Backed out for causing fenix opt failures in BrowserJourneyBaselineProfileGenerator
Thanks, I'll try again to land it with fix in BrowserJourneyBaselineProfileGenerator. Unfortunately this test was not part of the precommit test. I will work with implementer to make sure this is part of the fenix preset try.
Backed out for causing fenix bpgo failures @ LaunchIntentBaselineProfileGenerator
| Assignee | ||
Comment 10•11 months ago
|
||
Thanks again. Unfortunately those tests are flaky and I was passing consistently locally. I've created issues to track it and added @ignore and will try to land this change again. Sorry about this.
Comment 11•11 months ago
|
||
Comment 12•11 months ago
|
||
| bugherder | ||
Comment 13•10 months ago
|
||
(In reply to Roger Yang [:royang] from comment #10)
Thanks again. Unfortunately those tests are flaky and I was passing consistently locally. I've created issues to track it and added @ignore and will try to land this change again. Sorry about this.
Can you please link the issues you filed?
Updated•10 months ago
|
| Assignee | ||
Comment 14•10 months ago
|
||
These are the issues created Bug 1964970 and Bug 1965004
Comment 15•10 months ago
|
||
(In reply to Cosmin Sabou [:CosminS] from comment #12)
Perfherder has detected a mozperftest performance change from push 3cde666e79666af24391c4befbed34ece8aba58e.
If you have any questions, please reach out to a performance sheriff. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.
Improvements:
| Ratio | Test | Platform | Options | Absolute values (old vs new) |
|---|---|---|---|---|
| 79% | background-resource cpuTime-gpu-background-diff | android-hw-a55-14-0-aarch64-shippable | 27.20 -> 5.83 | |
| 73% | background-resource cpuTime-tab-50% | android-hw-a55-14-0-aarch64-shippable | 5,606.67 -> 1,530.00 | |
| 68% | background-resource cpuTime-tab-10% | android-hw-a55-14-0-aarch64-shippable | 4,711.60 -> 1,509.17 | |
| 68% | background-resource cpuTime-tab-50% | android-hw-a55-14-0-aarch64-shippable | 5,540.40 -> 1,782.50 | |
| 68% | background-resource cpuTime-tab-start | android-hw-a55-14-0-aarch64-shippable | 3,482.80 -> 1,124.17 |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a performance sheriff to do that for you.
You can run all of these tests on try with ./mach try perf --alert 45156
The following documentation link provides more information about this command.
Description
•