From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Hanna Reitz <hreitz@redhat.com>,
qemu-devel@nongnu.org, Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PATCH] Revert "check-block: replace -makecheck with TAP output"
Date: Mon, 7 Mar 2022 09:13:13 +0100 [thread overview]
Message-ID: <3137076a-d0b2-510e-8da5-446281dce70d@redhat.com> (raw)
In-Reply-To: <YiJE5n8CkFTX4Zqn@redhat.com>
On 04/03/2022 17.57, Daniel P. Berrangé wrote:
> On Tue, Feb 08, 2022 at 07:44:32AM -0500, Paolo Bonzini wrote:
>> This reverts commit d316859f4e28c74ab8b618895d2a5e0a865d3cf1. The
>> TAP output is inferior in that it does not include the diff for
>> failed tests.
>>
>> Reported-by: Peter Maydell <peter.maydell@linaro.org>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> tests/check-block.sh | 6 ++--
>> tests/qemu-iotests/check | 6 ++--
>> tests/qemu-iotests/meson.build | 1 -
>> tests/qemu-iotests/testenv.py | 30 +++++++++----------
>> tests/qemu-iotests/testrunner.py | 49 +++++++++++++++-----------------
>> 5 files changed, 44 insertions(+), 48 deletions(-)
>
> Peter mentioned that he's seeing the CentOS 8 CI job fail
> continuously: eg
>
> https://gitlab.com/qemu-project/qemu/-/jobs/2163919781
>
> [quote]
> 1/1 qemu:block / qemu-iotests qcow2 ERROR 163.04s 120 subtests passed
> Summary of Failures:
> 1/1 qemu:block / qemu-iotests qcow2 ERROR 163.04s 120 subtests passed
> Ok: 0
> Expected Fail: 0
> Fail: 1
> Unexpected Pass: 0
> Skipped: 0
> Timeout: 0
> Full log written to /home/gitlab-runner/builds/Jpwtyaz7/0/qemu-project/qemu/build/meson-logs/iotestslog.txt
> make: *** [/home/gitlab-runner/builds/Jpwtyaz7/0/qemu-project/qemu/tests/Makefile.include:156: check-block] Error 1
>
> [/quote]
>
> None of the individual tests are showing ERROR though, only the final
> status is error.
>
> We also don't have access to iotestslog.txt which is very annoying.
>
> When i run it locally I got the iotests.log and found that it
> contained an error message saying the TAP outout was malformed
> and couldn't be parsed.
>
> When I ran the iotests manually I confirmed this, it prints:
>
> ok qcow2 037
> ok qcow2 038
> ok qcow2 039
> ok qcow2 040
> ok qcow2 041
> [case not run] test_after_a_quorum_snapshot (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_cancel (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_cancel_after_ready (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_complete (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_device_not_found (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_image_not_found (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_medium_not_found (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_no_node_name (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_nonexistent_replaces (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_pause (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_with_other_parent (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_with_other_parents_after_mirror_start (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
> [case not run] test_wrong_sync_mode (__main__.TestRepairQuorum): formats ['quorum'] are not whitelisted
>
> ok qcow2 042
> ok qcow2 043
> ok qcow2 046
>
>
> All those '[case not run]' lines are invalid tap output. The
> need to start with a leading '#' to be treated as a diagnostic
> message. I briefly considered sending a patch, until I remember
> this change to stop using TAP.
A patch for fixing the TAP problem is already on the list and has been
queued by Hanna:
https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg05074.html
So that should hopefully fix the problem with the CentOS 8 CI job once it
gets merged.
Thomas
prev parent reply other threads:[~2022-03-07 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 12:44 [PATCH] Revert "check-block: replace -makecheck with TAP output" Paolo Bonzini
2022-02-08 14:40 ` Peter Maydell
2022-02-08 14:51 ` Thomas Huth
2022-02-08 16:21 ` Paolo Bonzini
2022-02-09 7:32 ` Thomas Huth
2022-03-04 16:57 ` Daniel P. Berrangé
2022-03-07 8:13 ` Thomas Huth [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=3137076a-d0b2-510e-8da5-446281dce70d@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=hreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).