Re: copy-before-write test failing (was: Re: [PULL 07/10] iotests: copy-before-write: add cases for cbw-timeout option)

[Vladimir Sementsov-Ogievskiy]

On 7/5/22 12:03, Thomas Huth wrote:
> On 14/06/2022 12.29, Vladimir Sementsov-Ogievskiy wrote:
> > From: Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
> >
> > Add two simple test-cases: timeout failure with
> > break-snapshot-on-cbw-error behavior and similar with
> > break-guest-write-on-cbw-error behavior.
> >
> > Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
> > Reviewed-by: Hanna Reitz <hreitz@redhat.com>
> > Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> > ---
> >   tests/qemu-iotests/tests/copy-before-write    | 81 +++++++++++++++++++
> >   .../qemu-iotests/tests/copy-before-write.out  |  4 +-
> >   2 files changed, 83 insertions(+), 2 deletions(-)
>
>   Hi!
>
> Seems like this test is failing in the CI on FreeBSD and macOS:
>
>   https://gitlab.com/qemu-project/qemu/-/jobs/2670729995#L5763
>   https://gitlab.com/qemu-project/qemu/-/jobs/2670729993#L3247
>
> Could you please have a look?

+AssertionError: 'wrot[102 chars]led: Operation timed out\nread 
1048576/1048576[72 chars]c)\n' != 'wrot[102 chars]led: Connection timed 
out\nread 1048576/104857[73 chars]c)\n'
+  wrote 524288/524288 bytes at offset 0
+  512 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+- write failed: Operation timed out
+?               ^^ ^^
++ write failed: Connection timed out
+?               ^^^^ ^


Seems just different representation of ETIMEDOUT error. I'll send a patch to 
allow both variants.


--
Best regards,
Vladimir