1527728 - Crash-stats is still showing 66.0b6 for Firefox as current, though 66.0b7 was released yesterday

Status: RESOLVED FIXED

(Socorro :: General, task, P2)

Description

[Liz Henry (:lizzard) (relman/hg->git project)]

Is this pulling automatically from product-details? Or does it need to be changed by hand with each beta?

Comment 1

[Liz Henry (:lizzard) (relman/hg->git project)]

Will, can you help out or help find someone to fix this? Thanks!

Comment 2

[Marcia Knous [:marcia]]

I have noticed that when we moved from Nightly 66->67 that Socorro was slow to pick up the change. My usual workaround is just to search for everything manually.

Comment 3

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

Socorro no longer looks a product-details for featured versions. It generates the list of versions based on what crash reports have been received. The list should be cached for an hour, so it should update faster than what you're seeing.

I'll look into it.

Comment 4

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

Attachment: pr 4826: bug 1527728: fix versions in nav bar

Comment 5

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

willkg merged PR #4826: "bug 1527728: fix versions in nav bar" in 87e414a.

Stage is still showing 66.0b6 and not 66.0b7 in the menus, but there are crash reports for 66.0b6 in Elasticsearch. Doing a deploy won't affect the cache since that's in memcached and isn't affected by deploys. Once this deploys to stage, I'll see if this fixes the problem and if so, push it to prod.

Comment 6

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

It's on stage and the 66.0b6 is still there, but no 66.0b7. Some possibilities:

1. It's still pulling the data from cache (likely) and I just need to wait like 30 minutes for the cache to expire and it to fetch the data with the increased _facets_size from Elasticsearch, or

2. The _facets_size needs to be bigger than 1,000, or

3. My theory is horribly wrong and the cause is elsewhere.

So... I waited.

I waited roughly 40 minutes. Then stage showed 66.0b7 while prod continues to show 66.0b6 as the latest in the 66 series.

I'm going to wait another hour to see if prod changes. I think it won't. But it's possible that it will. Then I'll push this to prod and over the next few weeks, we can see if the situation improves.

Comment 7

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

I waited an hour and then did some SuperSearch queries. This one has a _facets_size of 100 and doesn't have 66.0b7:

https://crash-stats.mozilla.com/api/SuperSearchUnredacted/?_facets=version&_facets_size=100&_results_number=0&date=%3E%3D2019-01-01&product=Firefox

If we increase the _facets_size to 1000, then it does have 66.0b7. That's sorted by crash report count. I think that proves the theory.

Right now 66.0b7 shows up at 118. Looks like it would have neede to get 5,000 crashes before it got into the top 100 versions showed up in the nav bar.

I'm going to push this to prod now.

Comment 8

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

Prod is showing 66.0b7 now. I'm pretty sure that fixes it and it'll be fine going forward. The 1000th facet has 7 crash reports, so it should update much faster.

Sorry about this!

Comment 9

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

66.0b8 was just released. I see 30 crash reports in Crash Stats right now. The nav bar has already updated and shows 66.0b8 in the listing.