From: Thomas Huth <thuth@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com, berrange@redhat.com, jsnow@redhat.com
Subject: Re: [PATCH] gitlab: Disable io-raw-194 for build-tcg-disabled
Date: Tue, 6 Jun 2023 21:11:30 +0200 [thread overview]
Message-ID: <1bfcf2f7-237c-895f-8879-6067ec221cb8@redhat.com> (raw)
In-Reply-To: <20230606162556.58110-1-richard.henderson@linaro.org>
On 06/06/2023 18.25, Richard Henderson wrote:
> This test consistently fails on Azure cloud build hosts in
> a way that suggests a timing problem in the test itself:
>
> --- .../194.out
> +++ .../194.out.bad
> @@ -14,7 +14,6 @@
> {"return": {}}
> {"data": {"status": "setup"}, "event": "MIGRATION", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}}
> {"data": {"status": "active"}, "event": "MIGRATION", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}}
> -{"data": {"status": "postcopy-active"}, "event": "MIGRATION", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}}
> {"data": {"status": "completed"}, "event": "MIGRATION", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}}
> Gracefully ending the `drive-mirror` job on source...
> {"return": {}}
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> .gitlab-ci.d/buildtest.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index 0f1be14cb6..000062483f 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -236,7 +236,7 @@ build-tcg-disabled:
> - cd tests/qemu-iotests/
> - ./check -raw 001 002 003 004 005 008 009 010 011 012 021 025 032 033 048
> 052 063 077 086 101 104 106 113 148 150 151 152 157 159 160 163
> - 170 171 183 184 192 194 208 221 226 227 236 253 277 image-fleecing
> + 170 171 183 184 192 208 221 226 227 236 253 277 image-fleecing
> - ./check -qcow2 028 051 056 057 058 065 068 082 085 091 095 096 102 122
> 124 132 139 142 144 145 151 152 155 157 165 194 196 200 202
> 208 209 216 218 227 234 246 247 248 250 254 255 257 258
That's fair to remove it: The iotests that are run here were only added here
because they were tested to succeed on the shared runners - if they were
running successfull everywhere, we would have added them to the "auto" group
instead so that they'd run during "make check-block". So if something is
failing on the private runners now, it's ok to remove them from this list here.
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-06-06 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 16:25 [PATCH] gitlab: Disable io-raw-194 for build-tcg-disabled Richard Henderson
2023-06-06 19:11 ` Thomas Huth [this message]
2023-06-06 19:24 ` Philippe Mathieu-Daudé
2023-06-06 19:36 ` Richard Henderson
2023-06-07 12:44 ` Stefan Hajnoczi
2023-06-07 14:26 ` Vladimir Sementsov-Ogievskiy
2023-06-07 14:38 ` Vladimir Sementsov-Ogievskiy
2023-06-07 15:06 ` Stefan Hajnoczi
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=1bfcf2f7-237c-895f-8879-6067ec221cb8@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@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).