./tools/fuzz-test.sh: line 201: /home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tools/valgrind-wireshark.sh: No such file or directory
This is why the valgrind fuzzing has been ineffective. I will take a look at fixing, though we may run into libtool issues as well (I'm not sure what ends up where at this point in the fuzz-bot). On Thu, Aug 15, 2013 at 3:31 AM, <[email protected]> wrote: > > The Buildbot has detected a new failure on builder Clang-Code-Analysis while building Wireshark (development). > Full details are available at: > http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/2063 > > Buildbot URL: http://buildbot.wireshark.org/trunk/ > > Buildslave for this Build: clang-code-analysis > > Build Reason: scheduler > Build Source Stamp: [branch master] ab8f63d76ca8a864dfb3dcbf525fecdb7b8bdef1 > Blamelist: Alexis La Goutte <[email protected]>,Anders Broman < [email protected]>,Evan Huus <[email protected]>,Guy Harris < [email protected]>,Jörg Mayer <[email protected]>,Martin Kaiser < [email protected]>,Martin Mathieson <[email protected]>,Pascal Quantin <[email protected]>,Stig Bjørlykke <[email protected]> > > BUILD FAILED: failed valgrind-wireshark > > sincerely, > -The Buildbot > > > > ___________________________________________________________________________ > Sent via: Wireshark-commits mailing list < [email protected]> > Archives: http://www.wireshark.org/lists/wireshark-commits > Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits > mailto:[email protected] ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
