-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Throttle / limit number of times we file an unreproducible crash #2533
Comments
Another spam-related issue from OSS-Fuzz is this one google/oss-fuzz#7040 Monorail query showing 100+ reports for same issue: https://bugs.chromium.org/p/oss-fuzz/issues/list?q=%22ASSERT%3A%20byte%20index%22%20json5format&can=1 |
Thanks @DavidKorczynski That looks like a separate issue with our grouping. All these testcases do end up getting grouped into the one group, but it happens too late after the bugs are filed. |
An alternative to creating a new issue to re-open the existing one. See also google/oss-fuzz#6791 |
* Only file bugs if grouper previous looked at the testcase. Part of #2533. * lint
Re-opening is something that doesn't fit well into our current bug triage workflow. For the unreproducible issues, we now only ever file them once. |
…2535) * Only file bugs if grouper previous looked at the testcase. Part of google#2533. * lint
This can lead to spam: https://bugs.chromium.org/p/oss-fuzz/issues/list?q=%22Sanitizer%20CHECK%20failure%22%20curl&can=1 and developer confusion: google/oss-fuzz#6879
The text was updated successfully, but these errors were encountered: