It seemed to start shortly after I added software updates. Unfortunately
I'm traveling and haven't had a chance to look into it closely.
On 2/26/13 11:52 AM, Evan Huus wrote:
> This has been failing for a while now, but I am unable to reproduce
> (though I don't have exactly XP x86). Anybody got a VM kicking around
> who can figure out what's going on here?
>
> On Mon, Feb 25, 2013 at 10:44 PM, <buildbot-no-reply@xxxxxxxxxxxxx> wrote:
>> The Buildbot has detected a new failure on builder Windows-XP-x86 while building Wireshark (development).
>> Full details are available at:
>> http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/4279
>>
>> Buildbot URL: http://buildbot.wireshark.org/trunk/
>>
>> Buildslave for this Build: windows-xp-x86
>>
>> Build Reason: scheduler
>> Build Source Stamp: 47898
>> Blamelist: morriss,wmeier
>>
>> BUILD FAILED: failed test.sh
>>
>> sincerely,
>> -The Buildbot
>>
>>
>>
>> ___________________________________________________________________________
>> Sent via: Wireshark-commits mailing list <wireshark-commits@xxxxxxxxxxxxx>
>> Archives: http://www.wireshark.org/lists/wireshark-commits
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits
>> 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
>
