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

Issue 696411 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Timeout in icu_break_iterator_utf32_fuzzer

Project Member Reported by ClusterFuzz, Feb 27 2017

Issue description

Cc: msrchandra@chromium.org
Components: Infra>Git
Labels: Test-Predator-Wrong M-58
Owner: riesa@chromium.org
Status: Assigned (was: Untriaged)
Assigning to the concern owner from the CL --
https://chromium.googlesource.com/chromium/src/+log/dd7a9eede66b8ab6d1b76c24d01010d7ad06cafa..e9b223cdc1ec6669545020702c93aeb707f2da76?pretty=fuller

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/af9b038a6bf7758c74df279bc15a77a907ee61af

@riesa -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by riesa@chromium.org, Feb 27 2017

Owner: mmoroz@chromium.org
This particular commit was done by mmoroz@. Re-assigning to him.
https://chromium.googlesource.com/chromium/deps/icu.git/+/ec5152fccfdf72281af53f863e3859c20f409153
Project Member

Comment 3 by ClusterFuzz, Feb 27 2017

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

Comment 4 by mmoroz@chromium.org, Feb 27 2017

Let's see if it reproduces with ASan build.
Project Member

Comment 5 by ClusterFuzz, Feb 28 2017

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

Comment 6 by ClusterFuzz, Apr 9 2017

Labels: OS-Mac
Project Member

Comment 7 by ClusterFuzz, Jun 7 2017

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6424815243362304 is flaky and no longer reproduces, so closing issue.

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

Sign in to add a comment