New issue
Advanced search Search tips

Issue 712696 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug

Blocking:
issue 62400



Sign in to add a comment

Timeout in pdf_fm2js_fuzzer

Project Member Reported by ClusterFuzz, Apr 18 2017

Issue description

Cc: npm@chromium.org dsinclair@chromium.org
Components: Internals>Plugins>PDF
Labels: M-60 Test-Predator-Wrong
Could someone please take a look?.
Thank you.
Project Member

Comment 3 by ClusterFuzz, Apr 19 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 4920904518991872 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Blocking: 62400
Cc: -dsinclair@chromium.org
Labels: ClusterFuzz-Wrong
Owner: dsinclair@chromium.org
Status: Available (was: Verified)
Don't see any reason why this would be fixed.
Status: WontFix (was: Available)
Bulk-WontFixing these bugs. This was a bug on ClusterFuzz side, see bug 717534. We will start seeing new testcases auto-filed in a day or two. We can't leave these open as ClusterFuzz won't autoverify them after ClusterFuzz-Wrong label.
Labels: -ClusterFuzz-Wrong
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.

Sign in to add a comment