Re: [Qemu-devel] Suggestion for testing framework

[Glauber Costa]

On Wed, Jun 4, 2008 at 7:28 AM, Avi Kivity <address@hidden> wrote:
> Paul Brook wrote:
>>
>> We were talking about a tester that does periodic long running tests off
>> svn trunk, and reports the results. Individual developers are not directly
>> involved.
>>
>>
>
> Even that is tremendously useful.  Once you identify a regression, it is
> easy to bisect and pinpoint the offending patch, which also locates the
> author.

Not that easy, regarding bisection. Qemu does not have an as strict
commit policy as the linux kernel, and you bet most of the commits
won't build fine by their own.

>
>> You're talking about some sort of testsuite that can be distributed to all
>> developers and reasonably run before every patch is submitted, which is a
>> significantly different beast.
>>
>> I'm pretty certain the proposed tests would not be suitable for routine
>> use by the majority of developers are part of normal developers. They will
>> be too large, probably take a long time to run, and contain proprietary
>> software that can't be redistributed.
>>
>
> There's no need to start at the screen while the test is running.
>  Proprietary software can be worked around by having the user provide a CD
> image and licensing keys in a configuration file.
>

That's a good solution, but we do have an awful lot of Free Software
that covers a wide range of qemu targets, right? So even if one does
not have, or does not want to run a CD, or so, it's still better than
nothing at all

-- 
Glauber Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."