Closed
Bug 1505080
Opened 6 years ago
Closed 6 years ago
Socorro is showing a Fennec 64.0 version that is really a beta
Categories
(Socorro :: Processor, task, P2)
Socorro
Processor
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: marcia, Assigned: willkg)
Details
https://crash-stats.mozilla.com/topcrashers/?product=FennecAndroid&version=64.0 The Build ID 20181101155334 I assume is a beta version. Is there a way to adjust this?
Assignee | ||
Comment 1•6 years ago
|
||
That's weird. I reprocessed 5 of them and they all came up with 64.0b6. I don't know what happened, but I'll reprocess all of them now.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Priority: -- → P2
Assignee | ||
Comment 2•6 years ago
|
||
All of those crashes have been reprocessed. I forget what gets cached where, so it might take up to an hour for the bad cached data to expire and topcrashers and menus to show up right. I'm going to keep this open to figure out what happened. The last thing any of us want to deal with is crash reports to be getting assigned weirdo versions like this. That's not helpful. I'll look into it more tomorrow. Sorry about this!
Comment 3•6 years ago
|
||
perhaps it was the same lag for new builds in buildhub that we've also seen for 64.0b6 desktop builds (& that should be addressed now with your fix from bug 1504281)
Assignee | ||
Comment 4•6 years ago
|
||
Philipp: Oh, you're right--I bet that is what happened! I coded the fix for bug #1504281 last week, but only pushed it to prod yesterday. With the old code that didn't degrade well, that's probably what would have happened in certain cases. I need to push out another fix tonight. Along with that is an admin page that'll let me see what the deal is with versions better. I'll know more after that goes out.
Assignee | ||
Comment 5•6 years ago
|
||
I haven't seen a repeat of this. I think Philipp's theory in comment #3 is right on--the timeline matches. Given that, I'm going to mark this as FIXED.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•