From: Paolo Bonzini <pbonzini@redhat.com>
To: Romain Naour <romain.naour@gmail.com>,
Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] meson: add tests option
Date: Wed, 3 Mar 2021 13:22:22 +0100 [thread overview]
Message-ID: <472c9809-8987-3c2c-c2b5-b99d637ace0f@redhat.com> (raw)
In-Reply-To: <8d5714d1-d92b-60fc-531f-73eb05852c8f@gmail.com>
On 02/03/21 22:14, Romain Naour wrote:
>> I disagree, without a use case the right thing to do is to check for fenv.h.
>> It's as easy as this:
> Is it ok if I take your patch to disable fp tests when fenv.h is missing and
> resend my patch with an updated commit log to disable all tests to save some
> build time?
To save build time you could also mark the tests as "build_by_default:
false". They should be built lazily when you run "make check".
Paolo
prev parent reply other threads:[~2021-03-03 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 22:07 [PATCH] meson: add tests option Romain Naour
2021-03-02 10:22 ` Thomas Huth
2021-03-02 11:08 ` Paolo Bonzini
2021-03-02 21:14 ` Romain Naour
2021-03-03 12:22 ` Paolo Bonzini [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=472c9809-8987-3c2c-c2b5-b99d637ace0f@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=romain.naour@gmail.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).