Closed Bug 984562 Opened 6 years ago Closed 6 years ago
Need to track 28
.0 Gecko release for 1 .3/1 .3T b2g
I would like to request data for tracking 28.0 Gecko. Sample of Buri Crash (1.3) : https://crash-stats.mozilla.com/report/index/c339fdad-457d-46f7-8d80-c7d862140317 Sample of Tarako Crash (1.3T) : https://crash-stats.mozilla.com/report/index/75ec6da7-5b38-473d-9033-034d72140317
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #0) > I would like to request data for tracking 28.0 Gecko. > > Sample of Buri Crash (1.3) : > https://crash-stats.mozilla.com/report/index/c339fdad-457d-46f7-8d80- > c7d862140317 Release Channel: hamachi/1.3.0/nightly We will very probably not get any reporting on those messed-up channels, esp. as RelEng promised to change those. > Sample of Tarako Crash (1.3T) : > https://crash-stats.mozilla.com/report/index/75ec6da7-5b38-473d-9033- > 034d72140317 Release Channel: default If that's an official testing build, it should at least report a beta-* channel as specified in https://developer.mozilla.org/en-US/docs/Crash_Reporting_Guide_for_Firefox_OS_Partners#Release_Channels - I really want to avoid adding channel rewrite info for short-lived testing versions. Shipped released should have the release-* channel set, but we can add those rewriting rules in place for them if mistakenly shipped with a different channel, like "default". And for custom-made builds from developers, those should show up with "default" channel and not be included in our reports if possible, to not have crashes in experimental code add noise (esp. as we don't have symbols for those builds anyhow).
Assignee: nobody → rhelmer
Status: NEW → ASSIGNED
Looking at bug 987450; it looks like Tarako will be using 28.1. Tracking them separately would be beneficial for the crash monitors.
I went ahead and added mappings for the crashes pointed to in comment 0 in this PR: https://github.com/mozilla/socorro/pull/1970 If these change we can should adjust or remove/add more as necessary, in new bugs. Eventually we will have a UI for this, but in the meantime let's continue to use bugs.
Commits pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/6b9a0fe7181a3d80a4a88d32e895dda51923a96b fix bug 984562 - track b2g 1.3 builds https://github.com/mozilla/socorro/commit/554facf6b8a22ba298e5a7af4f3ac9339d2673fc Merge pull request #1970 from rhelmer/bug984562-track-b2g-1_3 fix bug 984562 - track b2g 1.3 builds
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.