CHECK failure: result in icu_util.cc |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6588342438461440 Fuzzer: ochang_domfuzzer Job Type: windows_asan_content_shell Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: result in icu_util.cc base::i18n::InitializeICU content::ContentMainRunnerImpl::Initialize Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=487025:487028 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6588342438461440 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 18 2017
ClusterFuzz has detected this issue as fixed in range 487028:487032. Detailed report: https://clusterfuzz.com/testcase?key=6588342438461440 Fuzzer: ochang_domfuzzer Job Type: windows_asan_content_shell Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: result in icu_util.cc base::i18n::InitializeICU content::ContentMainRunnerImpl::Initialize Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=487025:487028 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=487028:487032 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6588342438461440 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jul 18 2017
ClusterFuzz testcase 6588342438461440 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jul 18 2017
I don't know if this is an infrastructure issue or what, but I don't think it's from any of my changes. This bug keeps getting refiled and then closed by CF [1]. Assigning to agable with the hope that he'll be able to find the right owner for CF infra issues. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=738424 https://bugs.chromium.org/p/chromium/issues/detail?id=740052 https://bugs.chromium.org/p/chromium/issues/detail?id=741600
,
Jul 18 2017
I don't think you'll be getting far by assigning verified bugs to people. Please file a new issue explaining the problem, possibly labelled with component: Tools>Stability>Clusterfuzz and/or Infra
,
Jul 18 2017
Yep, what machenbach said: a new bug in the Tools>Stability>Clusterfuzz component, pointing at this one and the others in your footnote, is the right way to go. |
|||
►
Sign in to add a comment |
|||
Comment 1 by msrchandra@chromium.org
, Jul 18 2017Labels: Test-Predator-Wrong-CLs M-61
Owner: littledan@chromium.org
Status: Assigned (was: Untriaged)