1555096 - Generate crash correlations for Fenix

Status: NEW

(Socorro :: Webapp, task)

Description

[Marcia Knous [:marcia]]

Maybe this is expected, but right now Fenix doesn't show in the correlations dropdown.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Marco: Do we generate correlations for Fenix? I'm pretty sure we don't, but I think the values in that dropdown is hard-coded in Crash Stats so if we did, I should add it.

Comment 2

[Marco Castelluccio [:marco]]

We are not generating them yet.
Do we need them for both Firefox for Android and Fenix? Or should we generate them only for Fenix?

Comment 3

[Marcia Knous [:marcia]]

Marco - I can see correlations already on the Firefox for Android side. So I think they are just needed for Fenix.

Comment 4

[Marcia Knous [:marcia]]

(In reply to Marco Castelluccio [:marco] (PTO until August 30) from comment #2)

We are not generating them yet.
Do we need them for both Firefox for Android and Fenix? Or should we generate them only for Fenix?

Hi Marco - Are any closer to having correlations yet? Thanks.

Comment 5

[Marco Castelluccio [:marco]]

I had to perform a migration of the job from ATMO (which is being deprecated) to Databricks. The migration is now done, so I can do this.

Two questions:

1. Do we still want Fennec correlations, or should I stop collecting them?
2. If the answer to 1 is "keep collecting", do we keep collecting correlations for nightly, beta and release, or just one of these channels?
3. To add Fenix, I need a way to know the released Fenix versions. For Firefox and Fennec, I'm using respectively https://product-details.mozilla.org/1.0/firefox_versions.json and https://product-details.mozilla.org/1.0/mobile_versions.json, but Fenix does not seem to be on product details. Should I use Firefox versions for Fenix, or is there another data source?

Comment 6

[Marcia Knous [:marcia]]

(In reply to Marco Castelluccio [:marco] from comment #5)

I had to perform a migration of the job from ATMO (which is being deprecated) to Databricks. The migration is now done, so I can do this.

Two questions:

1. Do we still want Fennec correlations, or should I stop collecting them?
2. If the answer to 1 is "keep collecting", do we keep collecting correlations for nightly, beta and release, or just one of these channels?
3. To add Fenix, I need a way to know the released Fenix versions. For Firefox and Fennec, I'm using respectively https://product-details.mozilla.org/1.0/firefox_versions.json and https://product-details.mozilla.org/1.0/mobile_versions.json, but Fenix does not seem to be on product details. Should I use Firefox versions for Fenix, or is there another data source?

(1) We definitely want to keep Fennec correlations.

Regarding the answers to (2) and (3), I asked the rest of Relman to weigh in via email. I will post when I get more information.

Comment 7

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

I dropped a note in release engineering team's design document for Fenix ship-it support to ensure we start documenting Fenix releases in product-details. JLund told me this is on the roadmap.

Comment 8

[Marcia Knous [:marcia]]

The answer to #2 is definitely yes as well.

Comment 9

[Marco Castelluccio [:marco]]

(In reply to Ritu Kothari (:ritu) from comment #7)

I dropped a note in release engineering team's design document for Fenix ship-it support to ensure we start documenting Fenix releases in product-details. JLund told me this is on the roadmap.

Is there a bug for this, so I can set it as blocking this one?

Comment 10

[Jordan Lund (:jlund)]

we can use bug 1568466 for now. This tracks Fenix getting on shipit which also blocks adding product-details for Fenix.