Bug 1697291 Comment 5 Edit History

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

In this case we are already doing so. With these buckets in place the fuzzer will still hit theses issues (fairly frequently in this case). This causes unnecessary overhead and can block code paths from being explored. We also run the risk of making buckets that are overly inclusive.

That said we understand resources are limited. Some issues do not have direct impact on end users and other more important tasks may take priority. 

We use `[fuzzblocker]` to indicate that, from the fuzzing perspective, this is important since in many cases it is not obvious. Fixing fuzzblockers really helps unblock the fuzzing pipeline.
In this case we are already doing so. With these buckets in place the fuzzer will still hit these issues (fairly frequently in this case). This causes unnecessary overhead and can block code paths from being explored. We also run the risk of making buckets that are overly inclusive.

That said we understand resources are limited. Some issues do not have direct impact on end users and other more important tasks may take priority. 

We use `[fuzzblocker]` to indicate that, from the fuzzing perspective, this is important since in many cases it is not obvious. Fixing fuzzblockers really helps unblock the fuzzing pipeline.

Back to Bug 1697291 Comment 5