qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
	qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, armbru@redhat.com, stefanha@redhat.com,
	eblake@redhat.com, hreitz@redhat.com, kwolf@redhat.com,
	peter.maydell@linaro.org
Subject: Re: [PULL 00/10] Block jobs & NBD patches
Date: Wed, 15 Jun 2022 07:39:16 -0700	[thread overview]
Message-ID: <a8ad29a5-73db-820b-089d-200c2875bc57@linaro.org> (raw)
In-Reply-To: <8b8ba4be-2713-7b8d-a7a1-398ee37f41a4@yandex-team.ru>

On 6/15/22 02:47, Vladimir Sementsov-Ogievskiy wrote:
> Also, could/should I run all these test pipelines on gitlab by hand before sending a PULL 
> request? Or can I rerun them on my qemu fork for debugging?

The first thing I'd try is make vm-build-<image> and make docker-test-full@<image>.

Either or both will reproduce the docker environment being used on gitlab.
If that fails to reproduce, it could be a difference in kernels, at which point I don't 
know how to advise.

It would be a good idea to run those test pipelines manually before the next PULL.


r~


      reply	other threads:[~2022-06-15 14:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 10:29 [PULL 00/10] Block jobs & NBD patches Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 01/10] block/copy-before-write: refactor option parsing Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 02/10] block/copy-before-write: add on-cbw-error open parameter Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 03/10] iotests: add copy-before-write: on-cbw-error tests Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 04/10] util: add qemu-co-timeout Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 05/10] block/block-copy: block_copy(): add timeout_ns parameter Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 06/10] block/copy-before-write: implement cbw-timeout option Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 07/10] iotests: copy-before-write: add cases for " Vladimir Sementsov-Ogievskiy
2022-07-05  9:03   ` copy-before-write test failing (was: Re: [PULL 07/10] iotests: copy-before-write: add cases for cbw-timeout option) Thomas Huth
2022-07-05  9:44     ` Vladimir Sementsov-Ogievskiy
2022-07-06 16:22     ` copy-before-write test failing Thomas Huth
2022-07-06 17:05       ` Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 08/10] nbd: trace long NBD operations Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 09/10] block: use 'unsigned' for in_flight field on driver state Vladimir Sementsov-Ogievskiy
2022-06-14 10:29 ` [PULL 10/10] MAINTAINERS: update Vladimir's address and repositories Vladimir Sementsov-Ogievskiy
2022-06-14 18:05 ` [PULL 00/10] Block jobs & NBD patches Richard Henderson
2022-06-15  9:47   ` Vladimir Sementsov-Ogievskiy
2022-06-15 14:39     ` Richard Henderson [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=a8ad29a5-73db-820b-089d-200c2875bc57@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    /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).