Updates:
Labels: -restrict-view-commit -deadline-approaching Deadline-Exceeded
Comment #6 on issue 31168 by sheriffbot: binutils:fuzz_readelf: Timeout in
fuzz_readelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31168#c6
This bug has exceeded our disclosure deadline. It has been
Updates:
Labels: Deadline-Approaching
Comment #5 on issue 31168 by sheriffbot: binutils:fuzz_readelf: Timeout in
fuzz_readelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31168#c5
This bug is approaching its deadline for being fixed, and will be automatically
derestricted withi
Comment #4 on issue 31168 by amo...@gmail.com: binutils:fuzz_readelf: Timeout
in fuzz_readelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31168#c4
No, sorry, I don't know that much about anything in oss-fuzz outside of
projects/binutils.
--
You received this message because:
1. Yo
Comment #3 on issue 31168 by p.ant...@catenacyber.fr: binutils:fuzz_readelf:
Timeout in fuzz_readelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31168#c3
> Perhaps the readelf tests ought to redirect output to /dev/null?
Alan, do you know how to do that ?
--
You received this messag
Comment #2 on issue 31168 by amo...@gmail.com: binutils:fuzz_readelf: Timeout
in fuzz_readelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31168#c2
This timeout is not caused by a bug in readelf, but is due to a testcase
producing 3.6G of output. It seems oss-fuzz infrastructure can't
