qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Christian Schoenebeck <qemu_oss@crudebyte.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v2 for-5.2] tests/9pfs: Mark "local" tests as "slow"
Date: Tue, 24 Nov 2020 09:04:58 +0100	[thread overview]
Message-ID: <20201124090458.138fda63@bahia.lan> (raw)
In-Reply-To: <8f6b304b-1a7c-e16d-c413-170605599347@redhat.com>

On Tue, 24 Nov 2020 08:54:38 +0100
Thomas Huth <thuth@redhat.com> wrote:

> On 24/11/2020 08.43, Greg Kurz wrote:
> > The "local" tests can fail on some automated build systems as
> > reported here:
> > 
> > https://lists.nongnu.org/archive/html/qemu-devel/2020-11/msg05510.html
> > 
> > This will need to be investigated and addressed later. Let's go for a
> > workaround in the meantime : mark the "local" tests as "slow" so that
> > they aren't executed with a simple "make check" like in the case above.
> > 
> > Reported-by: Cole Robinson <crobinso@redhat.com>
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > v2: - less noisy patch
> > ---
> >  tests/qtest/virtio-9p-test.c |    9 +++++++++
> >  1 file changed, 9 insertions(+)
> > 
> > diff --git a/tests/qtest/virtio-9p-test.c b/tests/qtest/virtio-9p-test.c
> > index 21e340fa5f43..92a498f24925 100644
> > --- a/tests/qtest/virtio-9p-test.c
> > +++ b/tests/qtest/virtio-9p-test.c
> > @@ -1456,6 +1456,15 @@ static void register_virtio_9p_test(void)
> >  
> >  
> >      /* 9pfs test cases using the 'local' filesystem driver */
> > +
> > +    /*
> > +     * XXX: Until we are sure that these tests can run everywhere,
> > +     * keep them as "slow" so that they aren't run with "make check".
> > +     */
> > +    if (!g_test_slow()) {
> > +        return;
> > +    }
> > +
> >      opts.before = assign_9p_local_driver;
> >      qos_add_test("local/config", "virtio-9p", pci_config,  &opts);
> >      qos_add_test("local/create_dir", "virtio-9p", fs_create_dir, &opts);
> 
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> 
> I assume you'll take this via the 9p tree? I don't have any other qtest
> patches pending right now, so I did not plan to send another pull request
> today...
> 

Yeah, I plan to do that later today.

Cheers,

--
Greg


  reply	other threads:[~2020-11-24  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24  7:43 [PATCH v2 for-5.2] tests/9pfs: Mark "local" tests as "slow" Greg Kurz
2020-11-24  7:54 ` Thomas Huth
2020-11-24  8:04   ` Greg Kurz [this message]
2020-11-24 11:40 ` Christian Schoenebeck

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=20201124090458.138fda63@bahia.lan \
    --to=groug@kaod.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu_oss@crudebyte.com \
    --cc=thuth@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).