From: Richard Henderson <richard.henderson@linaro.org>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, hreitz@redhat.com, kwolf@redhat.com,
thuth@redhat.com, jsnow@redhat.com
Subject: Re: [PATCH] iotests: fix copy-before-write for macOS and FreeBSD
Date: Tue, 5 Jul 2022 22:52:11 +0530 [thread overview]
Message-ID: <e5fa4843-31e1-9ce2-fd13-ffa1b6ee6f1e@linaro.org> (raw)
In-Reply-To: <20220705153708.186418-1-vsementsov@yandex-team.ru>
On 7/5/22 21:07, Vladimir Sementsov-Ogievskiy wrote:
> strerror() represents ETIMEDOUT a bit different in Linux and macOS /
> FreeBSD. Let's support the latter too.
>
> Fixes: 9d05a87b77 ("iotests: copy-before-write: add cases for cbw-timeout option")
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> ---
>
> As John and Thomas noted, the new iotests fails for FreeBSD and maxOS.
> Here is a fix. Would be great if someone can test it.
>
> I tried to push it by
>
> git push --force -o ci.variable="QEMU_CI=1"
>
> to my block branch, I get a blocked pipeline
> https://gitlab.com/vsementsov/qemu/-/pipelines/580573238
> but it doesn't have neither freebsd nor macos jobs.. How to get them?
You'd have to have an attached cirrus token.
Better to just use 'make vm-build-freebsd'.
> def test_timeout_break_guest(self):
> log = self.do_cbw_timeout('break-guest-write')
> + # macOS and FreeBSD tend to represent ETIMEDOUT as
> + # "Operation timed out", when Linux prefer
> + # "Connection timed out"
> + log = log.replace('Operation timed out',
> + 'Connection timed out')
Um, really? Matching strerror text? This is ultra-fragile.
Dare I say broken already.
r~
next prev parent reply other threads:[~2022-07-05 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 15:37 [PATCH] iotests: fix copy-before-write for macOS and FreeBSD Vladimir Sementsov-Ogievskiy
2022-07-05 17:22 ` Richard Henderson [this message]
2022-07-05 18:18 ` Vladimir Sementsov-Ogievskiy
2022-07-06 7:34 ` Thomas Huth
2022-07-06 8:56 ` Peter Maydell
2022-07-06 7:28 ` Thomas Huth
2022-07-06 10:26 ` Hanna Reitz
2022-07-06 11:29 ` Vladimir Sementsov-Ogievskiy
2022-07-06 14:46 ` Vladimir Sementsov-Ogievskiy
2022-07-06 16:51 ` Hanna Reitz
2022-07-12 7:15 ` Richard Henderson
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=e5fa4843-31e1-9ce2-fd13-ffa1b6ee6f1e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).