1488926 - test_automigration.js is going to permafail when the Gecko version number is bumped 65 on 2018-10-22

Status: VERIFIED FIXED

(Firefox :: Migration, defect, P1)

Description

[Andreea Pavel [:apavel]]

[Tracking Requested - why for this release]:

+++ This bug was initially created as a clone of Bug #1432488 +++

https://treeherder.mozilla.org/#/jobs?repo=try&revision=701dd8f52ed8236eb93a1bf297ef81997a391170&selectedJob=197614029

https://treeherder.mozilla.org/logviewer.html#?job_id=197614029&repo=try&lineNumber=2117

Histograms expire in firefox version 65.

Comment 1

[Sam Foster [:sfoster] (he/him)]

Doug, you handled this last time. Can you help triage this and get it in front of the right person?

Comment 2

[:Gijs (he/him)]

I defer to Doug here as to whether we are still planning experiments, or if we should remove all this code (or at least the telemetry).

Comment 3

[Alex Thayer [:alexical] (she/her)]

I haven't been actively engaged with this for a bit now. Chris, do you know if there's any plan/hope to automigrate users' data from other browsers in the nearish future? I'm trying to assess whether we should continue maintaining automigration code which is completely unused with the aspiration that we will use it in the future, or just cut it out now and reimplement it later if we happen to want that functionality. I'm leaning toward the latter if we don't think we'll want to invest resources into running automigration experiments and clearing out the remaining performance problems within the next year or two?

Comment 4

[Chris More [:cmore]]

(In reply to Doug Thayer [:dthayer] (Back from parental leave) from comment #3)
> I haven't been actively engaged with this for a bit now. Chris, do you know
> if there's any plan/hope to automigrate users' data from other browsers in
> the nearish future? I'm trying to assess whether we should continue
> maintaining automigration code which is completely unused with the
> aspiration that we will use it in the future, or just cut it out now and
> reimplement it later if we happen to want that functionality. I'm leaning
> toward the latter if we don't think we'll want to invest resources into
> running automigration experiments and clearing out the remaining performance
> problems within the next year or two?

Let's remove it. We don't have any current plans to re-enable it until we have a better understanding of a solution that would improve week 1 retention. We are going to be focused on getting users to import later on in their experience with Firefox instead of immediately on install.

Comment 5

[:Gijs (he/him)]

I'll look at fixing this this week or next.

Comment 6

[:Gijs (he/him)]

Attachment: Bug 1488926 - remove automigration code (already preffed off), r?dthayer

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/4f01697d7523
remove automigration code (already preffed off), r=dthayer

Comment 8

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/4f01697d7523