Well here's a good example. These two bugs are out-of-memory fuzz
failures that failed at the same time of day (one is master-1.12 and one
is master-1.10):
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11243
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11244
It certainly
And https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11149 is
potentially the same issue for 1.12 although it seems to have only
happened the once.
On Sat, May 30, 2015 at 10:27 PM, Evan Huus eapa...@gmail.com wrote:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11147 and its many
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11147 and its many
duplicates suggest a similar issue with the master buildbot.
On Sat, May 30, 2015 at 10:22 PM, Jeff Morriss
jeff.morriss...@gmail.com wrote:
There have been plenty of fuzz failures from the 1.10 branch in the past few
I ended up focusing on master-1.10 because there were so many bugs out
there. I guess that's just because most of the bugs against master were
already dup'd out!
I was wondering if maybe all the fuzz bots are running on the same
(virtual)machine and may be contending for memory (e.g., if two
There have been plenty of fuzz failures from the 1.10 branch in the past
few months, including:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11050
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11065
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11077
