search

nbp / meta-bugs

Find the transitive list of blocked bugs.
MIT License
0 stars 0 forks source link

Semi-automated crash stat analysis. #11

Open nbp opened 2 months ago

nbp commented 2 months ago

When a crash signature is available on the bug, we might want to provide a button to do some automated analysis, which should report some conclusions and their associated reasoning.

nbp commented 2 months ago

Crash-stat can be accessed using its API token: https://crash-stats.mozilla.org/api/tokens/ which implies adding the Auth-Token header as part of the request.

https://crash-stats.mozilla.org/api/RawCrash/?crash_id=710285dc-3684-4bc8-ab1a-2d30e0240422&format=meta can be used to retrieve the information from a single crash report. This might be useful if a crash report is opened by a user, but if the signature is not attached to the bug.

https://crash-stats.mozilla.org/api/RawCrash/?crash_id=710285dc-3684-4bc8-ab1a-2d30e0240422&format=raw&name=upload_file_minidump Can later be used if we want to automate the lookup of in-memory patterns. This might be useful to memory corruption in the binary when compared with the corresponding build-id, or to identify which code was responsible for generating the code (in which case we might need to revive seqrec project).

https://crash-stats.mozilla.org/api/SignaturesByBugs/?bug_ids=1886062 can be used to lookup signature names which are already attached to a bug.

An equivalent of the aggregate user facing feature can be achieved using the _facets of the SuperSearch API https://crash-stats.mozilla.org/api/SuperSearch/ , additionally the _columns can be used to collect information about all the corresponding crashes at once.

nbp commented 2 months ago

Using _results_number=0 with the SuperSearch can help limit the output to the _facets, which provides potentially a limited view to help focus the search and the interpretation without looking at individual reports.