-
Notifications
You must be signed in to change notification settings - Fork 1.3k
For #5182: Loading experiments on startup is slow, remove Fretboard!! #7510
Conversation
ba7f9b9
to
6ddb663
Compare
Codecov Report
@@ Coverage Diff @@
## master #7510 +/- ##
============================================
- Coverage 19.62% 18.94% -0.69%
+ Complexity 469 438 -31
============================================
Files 300 297 -3
Lines 11531 11367 -164
Branches 1561 1532 -29
============================================
- Hits 2263 2153 -110
+ Misses 9093 9046 -47
+ Partials 175 168 -7
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r+
@@ -64,6 +64,9 @@ fun Context.asFragmentActivity() = (this as? ContextThemeWrapper)?.baseContext a | |||
fun Context.getPreferenceKey(@StringRes resourceId: Int): String = | |||
resources.getString(resourceId) | |||
|
|||
@Suppress("unused") | |||
fun Context.isInExperiment(@Suppress("UNUSED_PARAMETER") experimentName: String): Boolean = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: would you mind adding a comment along the lines of Feature flags are not supported by Experimentor, we are currently looking into another way to handle them. See {issue number}
I'm probably good with Severin's review but adding myself for a quick skim when we've confirmed we're removing it. |
@mcomella We now have acknowledgement from the FxA team to remove it. They asked me to backlog an A-C issue for server-side flags, which I did. The only open question is if I should remove the |
@baron-severin and I agreed that it makes more sense to migrate this functionality to |
f6a4229
to
005a79d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I think moving these into FeatureFlags makes sense
bors r+ |
Configuration problembors.toml: not found |
How can I get it to re-run the UI tests at this point? |
iirc, we're not using bors so we do the old Focus thing: edit the PR title. |
Which I already did. |
profile |
We may want to land this tomorrow to be able to detect a monitor for possible regressions in other PRs in tonight's build. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Skimmed over and lgtm with Severin's review.
@colintheshots Can we also remove the fretboard (and any other) unused dependencies?
CI failure looks like a network error: rerunning. Note: I did not see any regressions from #7487 (comment) so I'm happy for this to merge. I had wanted to land that potential regression separately from this PR so that any improvements here weren't washed away by a possible known regression. Reminder from #7510 (review) that we should remove the fretboard dependencies. |
…ve Fretboard This removes Fretboard. The goal is to reduce cold startup costs associated with loading the experiments on the main thread. We currently have two experiments frameworks in use and should only require one.
005a79d
to
fb99387
Compare
This removes Fretboard. The goal is to reduce cold startup costs associated with loading the experiments on the main thread. We currently have two experiments frameworks in use and should only require one.
Pull Request checklist
After merge
To download an APK when reviewing a PR: