qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Juan Quintela" <quintela@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Peter Xu" <peterx@redhat.com>, "Bin Meng" <bmeng.cn@gmail.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 0/4] Speed up migration tests
Date: Fri, 19 Aug 2022 17:25:31 +0100	[thread overview]
Message-ID: <87r11c2oab.fsf@linaro.org> (raw)
In-Reply-To: <20220819053802.296584-1-thuth@redhat.com>


Thomas Huth <thuth@redhat.com> writes:

> We are currently facing the problem that the "gcov-gprof" CI jobs
> in the gitlab-CI are running way too long - which happens since
> the migration-tests have been enabled there recently.
>
> These patches now speed up the migration tests, so that the
> CI job should be fine again.

Awesome stuff, queued to testing/next, thanks.

-- 
Alex Bennée


      parent reply	other threads:[~2022-08-19 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  5:37 [PATCH 0/4] Speed up migration tests Thomas Huth
2022-08-19  5:37 ` [PATCH 1/4] tests/qtest/migration-test: Only wait for serial output where migration succeeds Thomas Huth
2022-08-19  5:38 ` [PATCH 2/4] tests/migration/aarch64: Speed up the aarch64 migration test Thomas Huth
2022-08-22 10:57   ` Daniel P. Berrangé
2022-08-19  5:38 ` [PATCH 3/4] tests/migration/i386: Speed up the i386 migration test (when using TCG) Thomas Huth
2022-08-22 10:58   ` Daniel P. Berrangé
2022-08-19  5:38 ` [PATCH 4/4] tests/qtest/migration-test: Remove duplicated test_postcopy from the test plan Thomas Huth
2022-08-22 10:59   ` Daniel P. Berrangé
2022-08-22 15:32     ` Dr. David Alan Gilbert
2022-08-19 16:25 ` Alex Bennée [this message]

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=87r11c2oab.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=bmeng.cn@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=thuth@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).