New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 693507 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in third_party_re2_fuzzer

Project Member Reported by ClusterFuzz, Feb 17 2017

Issue description

Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong M-58
Owner: mmoroz@chromium.org
Status: Assigned (was: Untriaged)
This bug looks similar to Bug Id -- 693507.
@mmoroz -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.
Project Member

Comment 2 by ClusterFuzz, Feb 17 2017

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://cluster-fuzz.appspot.com/testcase?key=4885014706913280

Comment 3 by mmoroz@google.com, Feb 17 2017

Cc: junyer@google.com kcc@chromium.org
Let's see if it reproduces with ASan.

Comment 4 by junyer@google.com, Feb 18 2017

After the recent commits, this input should not be particularly painful. (I'm not sure what Chromium has picked up so far.)

Comment 5 by mmoroz@chromium.org, Feb 18 2017

We are 4 commits behind ToT (https://chromium.googlesource.com/external/github.com/google/re2.git/+/596d73e6084a88c5394724978b10680dc929d197).

Looks like I need to do another update :)
Project Member

Comment 9 by ClusterFuzz, Feb 19 2017

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment