[llvm-bugs] Issue 12814 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: Timeout in llvm_llvm-isel-fuzzer--wasm32-O2

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #3 on issue 12814 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--wasm32-O2: Timeout in  
llvm_llvm-isel-fuzzer--wasm32-O2
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12814#c3

ClusterFuzz has detected this issue as fixed in range  
201902060426:201902070427.

Detailed report: https://oss-fuzz.com/testcase?key=5767470873313280

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--wasm32-O2
Fuzz target binary: llvm-isel-fuzzer--wasm32-O2
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address:
Crash State:
   llvm_llvm-isel-fuzzer--wasm32-O2

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201804120529:201804130530
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902060426:201902070427

Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=5767470873313280

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
instructions to reproduce this bug locally.

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

-- 
You received this message because:
   1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190207/65654f95/attachment.html>