Bugzilla

Hi, looks like the changes in Bug 1741205, that Gankra pointed out it will change some crash output, made crash signatures like `application crashed [@ libc.so.6 + 0x88650]` turn into these `application crashed [@ gsignal]`. Case in point [here](https://treeherder.mozilla.org/jobs?repo=autoland&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Csuccess%2Cusercancel%2Crunning%2Cpending%2Crunnable&searchStr=linux%2C18.04%2Cx64%2Cwebrender%2Cdebug%2Creftests%2Cwith%2Csoftware%2Cwebrender%2Cenabled%2Ctest-linux1804-64-qr%2Fdebug-crashtest-swr-e10s%2Cc&tochange=7b95b224608bddd747cbd81f43c1fbea888d63ea&fromchange=bf638341288eacbfd43ac6d8d3080e011ff1e8fb&selectedTaskRun=HTNprZ1sQMSX3nT23EXCFg.0).  
Looking closely at what was starred against this bug I've found: 
- these crashtests (445711.html and 441360.html) have had Bug 1737406 to be tracked and now are under this bug; the first log posted here https://bugzilla.mozilla.org/show_bug.cgi?id=1607713#c756 is actually Bug 1737406, the second one has `exit code -5` no assertion and looks like a singular failure for now, see https://treeherder.mozilla.org/intermittent-failures/bugdetails?startday=2021-11-21&endday=2021-11-28&tree=trunk&bug=1743143
- the mochitest failures that I've checked from https://treeherder.mozilla.org/intermittent-failures/bugdetails?startday=2021-11-20&endday=2021-11-27&tree=trunk&bug=1743142 all have `Assertion !xcb_xlib_threads_sequence_lost' failed.` and I think they belong back to Bug 1607713 cause all failures that have had `application crashed [@ libc.so.6 + 0x88650]` and that assertion in the past were starred against that one. 

Aryx, any thoughts on how we should proceed with the starrings here going forward?

Hi, looks like the changes in Bug 1741205, that Gankra pointed out it will change some crash output, made crash signatures like `application crashed [@ libc.so.6 + 0x88650]` turn into these `application crashed [@ gsignal]`. Case in point [here](https://treeherder.mozilla.org/jobs?repo=autoland&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Csuccess%2Cusercancel%2Crunning%2Cpending%2Crunnable&searchStr=linux%2C18.04%2Cx64%2Cwebrender%2Cdebug%2Creftests%2Cwith%2Csoftware%2Cwebrender%2Cenabled%2Ctest-linux1804-64-qr%2Fdebug-crashtest-swr-e10s%2Cc&tochange=7b95b224608bddd747cbd81f43c1fbea888d63ea&fromchange=bf638341288eacbfd43ac6d8d3080e011ff1e8fb&selectedTaskRun=HTNprZ1sQMSX3nT23EXCFg.0).  
Looking closely at what was starred against this bug I've found: 
- these crashtests (445711.html and 441360.html) have had Bug 1737406 to be tracked and now are under this bug; 
the first log posted here https://bugzilla.mozilla.org/show_bug.cgi?id=1607713#c756 is actually Bug 1737406, the second one has `exit code -5` no assertion and looks like a singular failure for now, see https://treeherder.mozilla.org/intermittent-failures/bugdetails?startday=2021-11-21&endday=2021-11-28&tree=trunk&bug=1743143
- the mochitest failures that I've checked from https://treeherder.mozilla.org/intermittent-failures/bugdetails?startday=2021-11-20&endday=2021-11-27&tree=trunk&bug=1743142 all have `Assertion !xcb_xlib_threads_sequence_lost' failed.` and I think they belong back to Bug 1607713 cause all failures that have had `application crashed [@ libc.so.6 + 0x88650]` and that assertion in the past were starred against that one. 

Aryx, any thoughts on how we should proceed with the starrings here going forward?