qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] buildbot failure in qemu on default_x86_64_rhel61


From: Andreas Färber
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_x86_64_rhel61
Date: Mon, 28 Jan 2013 14:30:39 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130105 Thunderbird/17.0.2

Am 28.01.2013 14:28, schrieb Anthony Liguori:
> Luiz Capitulino <address@hidden> writes:
> 
>> On Sat, 26 Jan 2013 23:25:11 +0100
>> address@hidden wrote:
>>
>>> The Buildbot has detected a new failure on builder default_x86_64_rhel61 
>>> while building qemu.
>>> Full details are available at:
>>>  
>>> http://buildbot.b1-systems.de/qemu/builders/default_x86_64_rhel61/builds/509
>>>
>>> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>>>
>>> Buildslave for this Build: kraxel_rhel61
>>>
>>> Build Reason: The Nightly scheduler named 'nightly_default' triggered this 
>>> build
>>> Build Source Stamp: [branch master] HEAD
>>> Blamelist: 
>>>
>>> BUILD FAILED: failed test
>>
>>   CC    tests/test-string-input-visitor.o
>>   LINK  tests/test-string-input-visitor
>> GTESTER tests/test-string-input-visitor
>> GTester: last random seed: R02S5d812c81f012364176697419b43c9bdd
>> make: *** [check-tests/test-string-input-visitor] Error 1
>> program finished with exit code 2
>> elapsedTime=6.389880
>>
>> gtester bug, maybe? I can't reproduce it here.
> 
> I doubt it I'd really like to have a backtrace and the full output from
> the test.
> 
> I'm running in a loop now in valgrind with that seed hoping I'll trigger
> something.

My guess was this could be the new string fuzzing test Blue added...

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg



reply via email to

[Prev in Thread] Current Thread [Next in Thread]