Bug 1861789 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Marco Castelluccio [:marco] from comment #2)
> There is a set of rules the bot follows to filter out crashes, most of them listed in the "Identify new actionable crashes" [...] Crashes matching the following are not automatically filed:
> - Hardware failure crashes
> - Crashes reported from the same person

Counterexamples where the bot might not be applying these properly:
- In bug 1863178, two out of the four crashes look to be from the same person, and potentially due to hardware issues (per the main paragraph in bug 1863178 comment 3)
- In bug 1863177, eight out of the ten crashes look to be from the same person. (see bug 1863177 comment 2.) Not sure if we can implicate hardware issues in this case.

(I'm not sure if BugBot mistakenly interpreted this^ crash volume as contributing to the "signal" here; it looks superficially like it did, but I suppose it might have been aware of these same-user/possible-hardware-issue factors and still filed because it decided that the remaining (small) crash volume was still enough to nudge it to file a bug.)
Revision 1 by
on 
(In reply to Marco Castelluccio [:marco] from comment #2)
> There is a set of rules the bot follows to filter out crashes, most of them listed in the "Identify new actionable crashes" [...] Crashes matching the following are not automatically filed:
> - Hardware failure crashes
> - Crashes reported from the same person

Counterexamples where the bot might not be applying these properly:
- In bug 1863178, two out of the four crashes look to be from the same person, and potentially due to hardware issues (per the main paragraph in bug 1863178 comment 3)
- In bug 1863177, eight out of the ten crashes look to be from the same person who was apparently testing a local web service on 127.0.0.1. (see bug 1863177 comment 2.)

(I'm not sure if BugBot mistakenly interpreted this^ crash volume as contributing to the "signal" here; it looks superficially like it did, but I suppose it might have been aware of these same-user/possible-hardware-issue factors and still filed because it decided that the remaining (small) crash volume was still enough to nudge it to file a bug.)

Back to Bug 1861789 Comment 6