Abrt in quipper::PerfReader::MaybeSwapEventFields |
|||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5127939127246848 Fuzzer: libFuzzer_chromeos_quipper_perf_reader_read_fuzzer Job Type: libfuzzer_ubsan_chromeos Platform Id: linux Crash Type: Abrt Crash Address: 0x000000000001 Crash State: quipper::PerfReader::MaybeSwapEventFields quipper::PerfReader::ReadPipedData quipper::PerfReader::ReadFromData Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_ubsan_chromeos&range=3110653:3111064 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5127939127246848 Issue filed automatically. See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
,
Nov 8
,
Nov 8
,
Nov 8
,
Nov 9
,
Nov 13
,
Dec 1
ClusterFuzz testcase 5127939127246848 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 4
ClusterFuzz testcase 5127939127246848 appears to be flaky, updating reproducibility label.
,
Dec 4
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This was caused by a bug in ClusterFuzz that has been fixed. Sorry again for the inconvenience.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by ClusterFuzz
, Nov 8Labels: ClusterFuzz-Auto-CC