Closed Bug 1884041 Opened 6 months ago Closed 5 months ago

fix create-a-bug links to work with java_exception

Categories

(Socorro :: General, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

Currently, for Java crashes, the create-a-bug link template depends on the java_stack_trace field in the processed crash which is derived from the JavaStackTrace annotation.

https://github.com/mozilla-services/socorro/blob/main/webapp/crashstats/crashstats/jinja2/crashstats/bug_comment.txt

We ultimately want to phase out JavaStackTrace in favor of JavaException.

We need to fix the create-a-bug links to work with java_exception field in the processed crash.

We may want to redo how the create-a-bug link works. Currently it's built using a Jinja2 template which is finicky about whitespace and incredibly difficult to maintain and change.

Further, Suhaib expressed interest in having a more exportable bit of code for generating the stacks for use in bug reports. They want to re-use it for automated bug creation.

Example Fenix crash report that has JavaException but no JavaStackTrace:

I refactored the code that creates the links in bug #1849266, so I can work on this now and it should be pretty straight forward to do a first pass.

Assignee: nobody → willkg
Status: NEW → ASSIGNED

This deployed to production just now in bug #1890341.

Here's an example. Crash report bp-eb6f852b-4656-4cf5-8350-fd91a0240408 which has a JavaException annotation, but no JavaStackTrace annotation. Before these changes, the comment would be:

Crash report: https://crash-stats.mozilla.org/report/index/eb6f852b-4656-4cf5-8350-fd91a0240408

Now the comment is:

Crash report: https://crash-stats.mozilla.org/report/index/eb6f852b-4656-4cf5-8350-fd91a0240408

Top 10 frames:

0  android.database.sqlite.SQLiteConnection  nativePrepareStatement  SQLiteConnection.java:-2
1  android.database.sqlite.SQLiteConnection  acquirePreparedStatement  SQLiteConnection.java:939
2  android.database.sqlite.SQLiteConnection  executeForString  SQLiteConnection.java:684
3  android.database.sqlite.SQLiteConnection  setJournalMode  SQLiteConnection.java:369
4  android.database.sqlite.SQLiteConnection  setWalModeFromConfiguration  SQLiteConnection.java:299
5  android.database.sqlite.SQLiteConnection  open  SQLiteConnection.java:218
6  android.database.sqlite.SQLiteConnection  open  SQLiteConnection.java:196
7  android.database.sqlite.SQLiteConnectionPool  openConnectionLocked  SQLiteConnectionPool.java:503
8  android.database.sqlite.SQLiteConnectionPool  open  SQLiteConnectionPool.java:204
9  android.database.sqlite.SQLiteConnectionPool  open  SQLiteConnectionPool.java:196
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: