Closed Bug 1145823 Opened 10 years ago Closed 10 years ago

B2G crash reports are not very helpful

Categories

(Socorro :: General, task)

Product:
Socorro
Component:
General
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: gwagner, Unassigned)

References

Details

We get crash reports from our testers that are not really helpful: https://crash-stats.mozilla.com/report/index/ca7b30d3-6731-4cc6-9473-ce2502150320#allthreads How can we improve this?
(In reply to Gregor Wagner [:gwagner] from comment #0) > We get crash reports from our testers that are not really helpful: > https://crash-stats.mozilla.com/report/index/ca7b30d3-6731-4cc6-9473- > ce2502150320#allthreads > > How can we improve this? It looks like symbols were not uploaded for this build, build automation should be doing this normally. Is it a nightly build or something else?
Where does this build come from? We only have symbols for Mozilla-built nightly or release builds from any channel or product, as well as for builds that some B2G partners upload symbols for.
See Also: → 1145769
Can you explain where you get your builds from?
Flags: needinfo?(jmitchell)
Gregor - This was from a nightly build - pulled from the PVT site and full-flashed. It's because currently, nightly does not have root access - please see bug 1121045
Flags: needinfo?(jmitchell)
root access should not be needed for crash reporting.
OK this is bug 1144865, B2G isn't uploading the index files with its text files correctly, so we can't quickly sync symbols from the old store to S3 (B2G also hasn't switched to uploading directly to S3 yet, I think that's bug 1085557) I'll go ahead and sync this and then reprocess this crash, which should fix this single crash, but we need one of those above bugs to be fixed for this not to happen anymore.
This crash has been reprocessed - let's follow up in the bugs from comment 6 for a more permanent fix.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
(In reply to Robert Helmer [:rhelmer] from comment #7) > This crash has been reprocessed - let's follow up in the bugs from comment 6 > for a more permanent fix. Thanks Robert. Bug 1085557 seems close.
You need to log in before you can comment on or make changes to this bug.