qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Yash Mankad" <ymankad@redhat.com>,
	"Lukáš Doktor" <ldoktor@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	qemu-devel@nongnu.org, "Cleber Rosa" <crosa@redhat.com>
Subject: Re: [Qemu-devel] Who is running QEMU automated tests, and when?
Date: Fri, 27 Apr 2018 05:58:44 +0200	[thread overview]
Message-ID: <fb1773e3-231c-f5ab-c7a5-828865b611ba@redhat.com> (raw)
In-Reply-To: <20180426142406.GO26812@redhat.com>

On 26.04.2018 16:24, Daniel P. Berrangé wrote:
> On Thu, Apr 26, 2018 at 11:22:36AM -0300, Eduardo Habkost wrote:
>> On Thu, Apr 26, 2018 at 03:14:00PM +0100, Daniel P. Berrangé wrote:
>>> On Thu, Apr 26, 2018 at 04:09:55PM +0200, Thomas Huth wrote:
>>>> 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.
>>>
>>> Hmm, we could get this done by travis. It has the concept of "cron jobs"
>>> for scheduling builds separately from pushes.
>>>
>>> So we could keep the current travis jobs unchanged, but then add an
>>> use of SPEED=slow when TRAVIS_EVENT_TYPE == "cron" in the travis.yml,
>>> so we can get SPEED=slow run once a day. Just have to be careful which
>>> jobs we make slow so we don't hit the 50 minute timeout.
>>
>> I expect SPEED=slow tests to eventually take longer than 50
>> minutes, but we can try this and see what happens.
> 
> We can run many jobs though so if qtests take longer than 50 mins, we could
> create 1 job per target arch.

That could work... individual "make check-qtest-xxx" should be short
enough, I hope.

 Thomas

  reply	other threads:[~2018-04-27  3:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 13:57 [Qemu-devel] Who is running QEMU automated tests, and when? Eduardo Habkost
2018-04-26 14:04 ` Peter Maydell
2018-04-26 21:51   ` Michael Clark
2018-05-09 15:53     ` Alex Bennée
2018-05-09 16:25       ` Thomas Huth
2018-04-26 14:09 ` Thomas Huth
2018-04-26 14:14   ` Daniel P. Berrangé
2018-04-26 14:22     ` Eduardo Habkost
2018-04-26 14:24       ` Daniel P. Berrangé
2018-04-27  3:58         ` Thomas Huth [this message]
2018-04-27  8:57           ` Daniel P. Berrangé
2018-04-26 14:25       ` Thomas Huth
2018-04-26 15:45         ` Cornelia Huck
2018-04-27  3:10 ` Fam Zheng
2018-04-27 19:23   ` Eduardo Habkost
2018-04-27 14:33 ` Anthony PERARD
2018-04-27 19:13 ` Lukáš Doktor
2018-05-08  9:56 ` Stefan Hajnoczi
2018-05-08 18:13   ` John Snow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb1773e3-231c-f5ab-c7a5-828865b611ba@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=ldoktor@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ymankad@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).