Evan Huus wrote:
In cases like bug 8045 [1], it would have been handy for it to say in the report somewhere which build-bot (version and OS) had found the error... is that reasonably easy to do?
There's only one buildbot doing the fuzz testing, isn't there? (It's the Clang-Code-Analysis one.)
BUT, I have to admit that I looked at bug 8045 when it first came in and was immensely confused: the bug was filed whiel that bot was in the middle of fuzz testing. I could not find the build which failed (that step) which generated the bug. Oops, yeah, I still have the bug open in a tab in order to say just that... <sigh>
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
