Re: [Qemu-devel] Who is running QEMU automated tests, and when?

[Thomas Huth <thuth@redhat.com>]

On 26.04.2018 15:57, Eduardo Habkost wrote:
> (Starting a new thread, for more visibility)
> 
> (This was: Re: [Qemu-devel] [RFC PATCH] tests/device-introspect: Test
> devices with all machines, not only with "none")
> 
> On Thu, Apr 26, 2018 at 01:54:43PM +0200, Markus Armbruster wrote:
[...]
>> I don't mind having make check SPEED=slow run more extensive tests.
>> Assuming we actually run them at least once in a while, which seems
>> doubtful.
> 
> We probably don't do that, but we really must be running a more
> extensive (and slower) test set at least once before every
> release.
> 
> Maybe some people are running SPEED=slow tests, or even more
> extensive test suites like avocado-vt once in a while, but we
> need to know who is running them, and when.

At least I am running "make check SPEED=slow" manually from time to
time, especially when we enter the hard freeze period.

> Today, the only test set I know people really run and would
> surely block a release is "make check [SPEED=quick]".

Same is true for the iotests, though they are run a little bit more
often than "check SPEED=slow", I think.

 Thomas


> So, for anybody that runs automated QEMU tests once in a while,
> can we know:
> 
> * What test cases are you running?  Where can we get more
>   information about the tests you run?
> * When do you run them?  What triggers a new test run?
> 
> Peter, do you have additional tests you run before merging a pull
> request?  Additional test sets run before tagging a release?
>