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

Issue 829420 link

Starred by 1 user
Status: Verified
Owner:
█ junyer@chromium.org
Last visit > 30 days ago
Closed: Jun 2018
Cc:
junyer@google.com
kcc@chromium.org
mmoroz@chromium.org
metzman@chromium.org
mbarbe...@chromium.org
infe...@chromium.org
och...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug

Blocked on:
issue 828032


Sign in to add a comment

Timeout in third_party_re2_fuzzer

Project Member Reported by ClusterFuzz, Apr 5 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6298425029820416

Fuzzer: libFuzzer_third_party_re2_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  third_party_re2_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=508782:508809

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6298425029820416

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
Project Member

Comment 1 by ClusterFuzz, Apr 5 2018

Cc: junyer@google.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Tweak a comment. by junyer@google.com - https://chromium.googlesource.com/external/github.com/google/re2/+/29a884523b4c6ba6a196103d2c8dec40ad48c6f8

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Comment 2 by junyer@google.com, Apr 5 2018 

That culprit is certainly not the culprit. ;)

Comment 3 by junyer@google.com, Apr 5 2018 

Also, what's the difference between libfuzzer_chrome_asan and libfuzzer_chrome_asan_debug?

Comment 4 by junyer@chromium.org, Apr 5 2018

Components: Tools>Stability>libFuzzer
Labels: Test-Predator-Wrong-CLs
Owner: junyer@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by junyer@google.com, Apr 5 2018 

I could potentially "fix" this by decreasing the fuzzer limit on \p and \P, but I want to understand why this "broke" now and not months ago. In particular, the unresolved issue with ASan memory footprint makes me suspect that we have another infrastructure issue.

Comment 6 by mmoroz@chromium.org, Apr 9 2018

Blockedon: 828032
Project Member

Comment 7 by ClusterFuzz, Jun 11 2018

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6298425029820416 appears to be flaky, updating reproducibility label.
Project Member

Comment 8 by ClusterFuzz, Jun 11 2018

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

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

Sign in to add a comment