1002492 - Some signatures for b2g 31.0a are not showing the reports.

Status: RESOLVED INVALID

(Socorro :: Webapp, task)

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

1. go to :
https://crash-stats.mozilla.com/report/list?product=B2G&range_value=7&range_unit=days&date=2014-04-27&signature=android%3A%3AGraphicBufferMapper%3A%3Aunlock%28native_handle+const%2A%29&version=B2G%3A31.0a1

2. look at the reports section

Expected: 8 reports
Actual: none

Note: the link was taken from the top crashers list for b2g 31.0a1

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

fyi

Comment 2

[Robert Helmer [:rhelmer]]

I have seen this before and thought it was from bug 928051, but 31.0a1 isn't mapped at all so maybe it's just a pre-existing issue for B2G builds..

The "Reports" tab uses the "reports" table in postgres directly so I suspect there's something unexpected about the data from B2G in the reports table.

Comment 3

[Lonnen :lonnen]

I think Rob has it. Rob or Selena -- if you get a chance could you look into this? If not I'll try to get to it before week's end.

Comment 4

[Robert Helmer [:rhelmer]]

(In reply to Chris Lonnen :lonnen from comment #3)
> I think Rob has it. Rob or Selena -- if you get a chance could you look into
> this? If not I'll try to get to it before week's end.

I didn't look into it deeper than commenting in comment 2. I will take a closer look.

Comment 5

[Robert Helmer [:rhelmer]]

OK tracked this down - the problem is that the release channel for these builds in reports table is "nightly-crespo" but in reports_clean it is "nightly".

I'm actually not sure why these are getting let into reports_clean table, this isn't one that we're mapping e.g. bug 928051.

Maybe we're letting anything with a channel like 'nightly%' in - I'll dig into it, but Selena might know. If that's the case then we just need to adjust this query, if not then I'd like to know why these are showing up in reporting at all before applying a "fix" like that.

Comment 6

[Selena Deckelmann :selenamarie :selena]

(In reply to Robert Helmer [:rhelmer] from comment #5)
> OK tracked this down - the problem is that the release channel for these
> builds in reports table is "nightly-crespo" but in reports_clean it is
> "nightly".
> 
> I'm actually not sure why these are getting let into reports_clean table,
> this isn't one that we're mapping e.g. bug 928051.
> 
> Maybe we're letting anything with a channel like 'nightly%' in - I'll dig
> into it, but Selena might know. If that's the case then we just need to
> adjust this query, if not then I'd like to know why these are showing up in
> reporting at all before applying a "fix" like that.

Yes, in the table 'release_channel_matches' we allow anything that starts with nightly: 

 Nightly         | nightly%


I imagine this was an ancient requirement baked into the reports_clean transforms. Happy to remove it but it may then break ancient assumptions.

Comment 7

[Robert Helmer [:rhelmer]]

(In reply to Selena Deckelmann :selenamarie :selena from comment #6)
> (In reply to Robert Helmer [:rhelmer] from comment #5)
> > OK tracked this down - the problem is that the release channel for these
> > builds in reports table is "nightly-crespo" but in reports_clean it is
> > "nightly".
> > 
> > I'm actually not sure why these are getting let into reports_clean table,
> > this isn't one that we're mapping e.g. bug 928051.
> > 
> > Maybe we're letting anything with a channel like 'nightly%' in - I'll dig
> > into it, but Selena might know. If that's the case then we just need to
> > adjust this query, if not then I'd like to know why these are showing up in
> > reporting at all before applying a "fix" like that.
> 
> Yes, in the table 'release_channel_matches' we allow anything that starts
> with nightly: 
> 
>  Nightly         | nightly%
> 
> 
> I imagine this was an ancient requirement baked into the reports_clean
> transforms. Happy to remove it but it may then break ancient assumptions.

Thanks for digging that up! It explains the behavior we're seeing here at least.

I think it'd make the most sense to fix the reports tab to be consistent at this point.

Comment 8

[Robert Kaiser]

I actually wonder why we put up the nightly-* channels in the signature summary, but they should always be shown in the reports table for sure.

Comment 9

[Robert Helmer [:rhelmer]]

Not working on this currently - is this bug still useful/actionable?

Comment 10

[Peter Bengtsson [:peterbe]]

B2g.