Timeout in gn_parser_fuzzer |
|||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5535224357453824 Fuzzer: libfuzzer_gn_parser_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout Crash Address: Crash State: gn_parser_fuzzer Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=438777:438804 Minimized Testcase (5.10 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94WzPuQGwY51clMAB2kDY1ZvC88asU7fqt9coeTts3WYG_SxX2Qh3sAyKwebOKPfiPAuQ0VSQqZrsMzRJDYoRNo_UZnYtLXEqz-Sp4GTYK2sT2Bs4C82qd_B5Ez5SVvQiUf80onpcO1sJqTh1PIw-DijAjEfg?testcase_id=5535224357453824 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Dec 19 2016
Find it and CL did not provide any possible suspect. Using Code Search for the file, "gn_parser_fuzzer" assigning to the concern owner. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/e47a47636163bd171399c6426e834837a52b75b7 @thakis -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Jun 7 2017
ClusterFuzz testcase 5535224357453824 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 |
|||
Comment 1 by 00sssom...@gmail.com
, Dec 18 2016