The XP buildbot had quite a few error dialogs open complaining about a
runtime error in wmem_test.exe. I closed them and it appears to run fine
now. Process Explorer didn't show any unusual memory usage when I ran
the test by hand.
On 5/5/14 6:14 AM, Evan Huus wrote:
> I'm really not sure what's causing the wmem test suite to hang like this
> (and only on XP...) - the lack of additional output from the buildbot is
> confusing. Gerald, is this easily reproducible if you run ./wmem_test
> directly on the XP bot?
>
>
> On Mon, May 5, 2014 at 9:07 AM, <buildbot-no-reply@xxxxxxxxxxxxx
> <mailto:buildbot-no-reply@xxxxxxxxxxxxx>> wrote:
>
> The Buildbot has detected a new failure on builder Windows XP x86
> while building wireshark.
> Full details are available at:
> http://buildbot.wireshark.org/trunk/builders/Windows%20XP%20x86/builds/8991
>
> Buildbot URL: http://buildbot.wireshark.org/trunk/
>
> Buildslave for this Build: windows-xp-x86
>
> Build Reason: scheduler
> Build Source Stamp: [branch master]
> 402bbcbd05cf50b2c3db565e54cf9012ab5b5db2
> Blamelist: Evan Huus <eapache@xxxxxxxxx <mailto:eapache@xxxxxxxxx>>
>
> BUILD FAILED: failed test.sh
>
> sincerely,
> -The Buildbot
>
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-commits mailing list
> <wireshark-commits@xxxxxxxxxxxxx
> <mailto:wireshark-commits@xxxxxxxxxxxxx>>
> Archives: http://www.wireshark.org/lists/wireshark-commits
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits
> mailto:wireshark-commits-request@xxxxxxxxxxxxx
> <mailto:wireshark-commits-request@xxxxxxxxxxxxx>?subject=unsubscribe
>
>
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>