I don't really get this - it happens inconsistently that the "fast" allocator takes longer to run than the "block" allocator. The fast allocator does much less work, and runs substantially faster than the block allocator everywhere I've tested it.
I don't know what glib's timing mechanism is like, but is it possible the underlying machine is busy, so the wall-clock time is varying a lot? I'm tempted to just disable the test, but that feels wrong. On Sun, Jul 20, 2014 at 12:20 PM, <buildbot-no-re...@wireshark.org> wrote: > The Buildbot has detected a new failure on builder Windows 8.1 x86 while > building wireshark. > Full details are available at: > > http://buildbot.wireshark.org/trunk/builders/Windows%208.1%20x86/builds/261 > > Buildbot URL: http://buildbot.wireshark.org/trunk/ > > Buildslave for this Build: windows-8.1-x86 > > Build Reason: scheduler > Build Source Stamp: [branch master] > bb53fba9520916c17de09eb6572529a44033dba5 > Blamelist: Gerald Combs <ger...@wireshark.org> > > BUILD FAILED: failed test.sh > > sincerely, > -The Buildbot > > > > ___________________________________________________________________________ > Sent via: Wireshark-commits mailing list < > wireshark-comm...@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-commits > Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits > mailto:wireshark-commits-requ...@wireshark.org > ?subject=unsubscribe >
___________________________________________________________________________ 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
