Exposing Android_CPU_ABI, Android_Manufacturer, Android_Model, Android_Version in crash report UI

VERIFIED FIXED in 18

Status

Socorro
Webapp
VERIFIED FIXED
6 years ago
5 years ago

People

(Reporter: Robert Kaiser, Assigned: espressive)

Tracking

unspecified
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
The raw JSON provides a number of Android-specific fields, some of which we'd like to see in the UI for individual crash reports to make crash investigation easier.

Here's some sample reports that show this info, with a sample of what info I'm talking about (as not everyone has access to see that info):

https://crash-stats.mozilla.com/rawdumps/568ff2bd-0067-41a9-b68f-8e54e2120724.json
Android_Hardware: "grouper", Android_Device: "grouper", Android_CPU_ABI: "armeabi-v7a", Android_Manufacturer: "asus", Android_Brand: "google", Android_Model: "Nexus 7", Android_Version: "16 (REL)", Android_Board: "grouper",

https://crash-stats.mozilla.com/rawdumps/4cb42586-7205-4043-8792-f377f2120719.json
Android_Hardware: "spica", Android_Device: "spica", Android_CPU_ABI: "armeabi-v6l", Android_Manufacturer: "samsung", Android_Brand: "samsung", Android_Model: "GT-I5700", Android_Version: "10 (REL)", Android_Board: "spica",

The latter is from the currently quite interesting bunch of new armv6 builds, for example.

Of those fields, we should expose Android_CPU_ABI, Android_Manufacturer, Android_Model, Android_Version in the report/index UI.
The version should be labeled as "Android API version" so that it's not confused with the Android OS version (which it corresponds to but doesn't match).

Ideally, I'd envision the addition to the crash report table to look like this:

+---------------------+-----------------------------------------+
| Device              | <Android_Manufacturer> <Android_Model>  |
+---------------------+-----------------------------------------+
| Android API Version | <Android_Version>                       |
+---------------------+-----------------------------------------+
| Android CPU ABI     | <Android_CPU_ABI>                       |
+---------------------+-----------------------------------------+

If this (the device line) is too hard for some reason, a simpler to implement variant can be done with the two fields in separate lines.

As I hope this should be quite simple to do, I hope this can be added very soon.
(Assignee)

Updated

6 years ago
Assignee: nobody → sneethling
Target Milestone: --- → 19
(Assignee)

Comment 1

6 years ago
Sent pull request: https://github.com/mozilla/socorro/pull/748

TEST CASE
---------

Navigate to an individual report for FennecAndroid, if the fields requested above in the bug is set, the fields in the following format will be displayed as part of the main table.

+---------------------+-----------------------------------------+
| Device              | <Android_Manufacturer> <Android_Model>  |
+---------------------+-----------------------------------------+
| Android API Version | <Android_Version>                       |
+---------------------+-----------------------------------------+
| Android CPU ABI     | <Android_CPU_ABI>                       |
+---------------------+-----------------------------------------+

Comment 2

6 years ago
Commits pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/e7ad95771e1fda69717c04244b13d22b91a5de32
adding additional line items to white list for Android fixes bug 777372

https://github.com/mozilla/socorro/commit/c1e0dd655ce3b0abb89d83b00527752508ba47fc
Merge pull request #748 from ossreleasefeed/expose-android-line-items-in-ui-777372

adding additional line items to white list for Android fixes bug 777372

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

6 years ago
Target Milestone: 19 → 18
Created attachment 652807 [details]
qa - reopened - parsing error

Reopened for clarification

I'm not sure if this is a defect, is the information provided by OS Version being parsed correctly?

https://crash-stats.allizom.org/report/index/3cda63a0-37cc-4d0a-8451-a3c542120811
+------------+--------------------------------------------------------------------------+
| OS         | Linux                                                                    |
+------------+--------------------------------------------------------------------------+
| OS Version | 0.0.0 Linux 2.6.35.7+ #1 SMP PREEMPT Mon Apr 30 04:51:34 UTC 2012 armv7l |
+------------+--------------------------------------------------------------------------+
|Build Arch  | arm                                                                      |
+------------+--------------------------------------------------------------------------+
(Reporter)

Comment 4

6 years ago
(In reply to Matt Brandt [:mbrandt] from comment #3)
> I'm not sure if this is a defect, is the information provided by OS Version
> being parsed correctly?

I'm not sure what you mean, for one thing, that field is correct as it is, for he other, thios bug didn't touch that "OS Version" (or "Build Arch") field at all.
> that field is correct
Thanks Kairo -- I wasn't sure if the string "0.0.0 Linux 2.6.35.7+ #1 SMP PREEMPT Mon Apr 30 04:51:34 UTC 2012 armv7l" was correct.
Status: RESOLVED → VERIFIED
(Reporter)

Updated

5 years ago
Blocks: 853452
(Reporter)

Updated

5 years ago
Blocks: 853455
You need to log in before you can comment on or make changes to this bug.