Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

This issue looks similar to  bug 829420 , hence assigning to the same owner for more updates.

junyer@ Could you please take a look in to this issue?

Thanks!

F(\PP\PL){995} is the minimised testcase, but that shouldn't be possible as per https://github.com/google/re2/blob/master/re2/parse.cc#L46-L51. Is the FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION macro not being defined anymore?

https://chromium.googlesource.com/chromium/src/+/2b4c02961570955e40d85646feb0865bb79fe661 looks like the culprit. Hi, mmoroz. :)

https://github.com/google/re2/blob/master/re2/re2.cc#L381-L387 is another place where the FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION macro is used, so I imagine that another timeout will be reported in the near future.

P.S. Surely RE2 cannot be the only project experiencing this problem? Many projects are using the macro because (I presume) http://libfuzzer.info#fuzzer-friendly-build-mode told them to use it. I expect that fuzzing without defining the macro that means "we are fuzzing you" will be troublesome.

Good catch! For some reason, we don't use optimize_for_fuzzing with debug build:
https://build.chromium.org/deprecated/chromium.fyi/builders/Libfuzzer%20Upload%20Linux%20ASan%20Debug/builds/12971

https://logs.chromium.org/v/?s=chromium%2Fbb%2Fchromium.fyi%2FLibfuzzer_Upload_Linux_ASan_Debug%2F12971%2F%2B%2Frecipes%2Fsteps%2Fgenerate_build_files%2F0%2Fstdout


We do use it for all the others, I've just verified.

junyer@, thanks for the investigation! I'll fix this.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8b309f7cd5c104c38428dbe4b0202f44859a104a

commit 8b309f7cd5c104c38428dbe4b0202f44859a104a
Author: Max Moroz <mmoroz@chromium.org>
Date: Thu Jun 14 17:09:11 2018

Enable optimize_for_fuzzing GN flag for libFuzzer ASan Debug configuration.

The flag is being used for all other configurations for a while. Looks like
we've forgotten to add it for the Debug one when it's been implemented.

Bug:  852391 
Change-Id: I2f3fbd4639fdb81b304f0abdd0c8fe6f3d1dbcb3
Reviewed-on: https://chromium-review.googlesource.com/1100964
Reviewed-by: Jonathan Metzman <metzman@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567318}
[modify] https://crrev.com/8b309f7cd5c104c38428dbe4b0202f44859a104a/tools/mb/mb_config.pyl

ClusterFuzz has detected this issue as fixed in range 567310:567338.

Detailed report: https://clusterfuzz.com/testcase?key=5142404647354368

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=562498:562507
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=567310:567338

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

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5142404647354368 is verified as fixed, so closing issue as verified.

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