958380 - B2G 28.0a1 version is producing 404s across links

Status: VERIFIED FIXED

(Socorro :: Webapp, task)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

Right now, if you:

1. Load https://crash-stats.allizom.org/home/products/B2G
2. Click on any of the following:

A) Top Crashers (https://crash-stats.mozilla.com/topcrasher/products/B2G/versions/28.0a1?days=7)
B) Top Changers (https://crash-stats.mozilla.com/topchangers/products/B2G/versions/28.0a1?days=7)
C) Top Plugin Crashers (https://crash-stats.mozilla.com/topcrasher/products/B2G/versions/28.0a1/crash_type/plugin?days=7)

...you'll get a/404(s)

Our automation caught this, across: dev, staging, and prod.

This really shouldn't be happening - might be an existing bug on this, but we should fix this ASAP -- version that are featured on a product's homepage should *never* 404.

Comment 1

[Robert Helmer [:rhelmer]]

Haven't looked into this yet - noticed that 29.0a1 is now "a1" (aka nightly) now.

Since topcrash and other reports don't work for B2G yet, I think the bigger deal is that versions are not selectable on https://crash-stats.allizom.org/query/?product=B2G#advanced

B2G is on a different release cycle, I suspect that older releases have timed out of the system. I'll check that.

Comment 2

[Robert Helmer [:rhelmer]]

(In reply to Robert Helmer [:rhelmer] from comment #1)
> B2G is on a different release cycle, I suspect that older releases have
> timed out of the system. I'll check that.

Yeah this is the problem:

breakpad=> select * from product_versions where product_name = 'b2g' and sunset_date >= '2014-01-10';
 product_version_id | product_name | major_version | release_version | version_s
tring | beta_number | version_sort  | build_date | sunset_date | featured_versio
n | build_type | has_builds | is_rapid_beta | rapid_beta_id 
--------------------+--------------+---------------+-----------------+----------
------+-------------+---------------+------------+-------------+----------------
--+------------+------------+---------------+---------------
               1550 | B2G          | 18.0          | 18.0            | 18.0b1   
      |           1 | 018000000b001 | 2013-04-18 | 2014-04-30  | f              
  | beta       | f          | f             |              
               1549 | B2G          | 18.0          | 18.0            | 18.0b    
      |           0 | 018000000r000 | 2013-04-18 | 2014-04-30  | t              
  | beta       | t          | t             |              
               2043 | B2G          | 29.0          | 29.0a1          | 29.0a1   
      |             | 029000000a001 | 2013-12-10 | 2014-02-11  | t              
  | nightly    | t          | f             |              
(3 rows)

breakpad=>

Comment 3

[Robert Helmer [:rhelmer]]

:kairo - any thoughts on what versions of B2G should be "active" in Socorro? Most of them have expired again. Also do you happen to know what the release schedule is for B2G in terms of what the expiration ("sunset date") should be set to for releases that ftpscraper picks up?

I remember we had to do this not long ago, would be nice to teach Socorro to treat B2G releases differently.

Comment 4

[Robert Kaiser]

What we have right now is OK, though we probably should have a 26.0 there and some kind of 28 version at some point, but I do not expect any usable reports on Socorro before bug 928051 is solved, so until then we should just ignore this.

Comment 6

[Robert Helmer [:rhelmer]]

Ignoring per comment 4

Comment 7

[Matt Brandt [:mbrandt]]

Bumping to QA verified since the top crashers list for featured versions no longer 404's - https://crash-stats.allizom.org/home/products/B2G

I agree with stephend in that a featured product should never 404