Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (developme
From: Pascal Quantin <pascal.quantin@xxxxxxxxx>
Date: Sat, 22 Jun 2013 17:33:07 +0200
Hi Evan,

I could not reproduce it either on my Windows XP box.

Regards,
Pascal.


2013/6/22 Evan Huus <eapache@xxxxxxxxx>
Running

./wmem_test --verbose --seed=R02S7c3c1e743f8aa20695f4377c8b1c40c8

Should produce exactly the same run (with the same output and
hopefully the same crash) as the buildbot saw.

On Fri, Jun 21, 2013 at 1:33 AM, Graham Bloice
<graham.bloice@xxxxxxxxxxxxx> wrote:
> OK for me also on XP x32, although I'm not sure how to feed in the seed from
> the failing test run.
>
> Graham
>
>
> On 20 June 2013 16:56, Pascal Quantin <pascal.quantin@xxxxxxxxx> wrote:
>>
>> Failed to reproduce it on my side also, but I was running on Windows 7
>> x64. I will not have access to my XP x32 box before I go back home in 2
>> days.
>>
>> Regards,
>> Pascal.
>>
>>
>> 2013/6/21 Evan Huus <eapache@xxxxxxxxx>
>>>
>>> I am unable to reproduce even with the random seed listed in the
>>> output (./wmem_test --seed=R02S7c3c1e743f8aa20695f4377c8b1c40c8).
>>> Valgrind shows no errors. Is anybody else seeing misbehaviour here?
>>>
>>> Thanks,
>>> Evan
>>>
>>> On Thu, Jun 20, 2013 at 4:40 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/5505
>>> >
>>> > Buildbot URL: http://buildbot.wireshark.org/trunk/
>>> >
>>> > Buildslave for this Build: windows-xp-x86
>>> >
>>> > Build Reason: scheduler
>>> > Build Source Stamp: 50091
>>> > Blamelist: eapache,martink,pascal
>>> >
>>> > 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
>>
>>
>>
>>
>> ___________________________________________________________________________
>> 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
>
>
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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