From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] cirrus: use V=1 when running tests on FreeBSD and macOS
Date: Wed, 07 Oct 2020 15:59:59 +0100 [thread overview]
Message-ID: <87o8leytcg.fsf@linaro.org> (raw)
In-Reply-To: <20201007140103.711142-1-pbonzini@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Using "V=1" makes it easier to identify hanging tests, especially
> since they are run with -j1. It is already used on Windows builds,
> do the same for FreeBSD and macOS.
>
> Cc: Alex Bennée <alex.bennee@linaro.org>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Queued to prepr/misc-testing-gitdm-plugin-fixes, thanks.
> ---
> .cirrus.yml | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/.cirrus.yml b/.cirrus.yml
> index d58782ce67..4d236fdefa 100644
> --- a/.cirrus.yml
> +++ b/.cirrus.yml
> @@ -15,7 +15,7 @@ freebsd_12_task:
> - cd build
> - ../configure --enable-werror || { cat config.log; exit 1; }
> - gmake -j$(sysctl -n hw.ncpu)
> - - gmake -j$(sysctl -n hw.ncpu) check
> + - gmake -j$(sysctl -n hw.ncpu) check V=1
>
> macos_task:
> osx_instance:
> @@ -29,7 +29,7 @@ macos_task:
> --extra-cflags='-Wno-error=deprecated-declarations'
> || { cat config.log; exit 1; }
> - gmake -j$(sysctl -n hw.ncpu)
> - - gmake check
> + - gmake check V=1
>
> macos_xcode_task:
> osx_instance:
> @@ -43,7 +43,7 @@ macos_xcode_task:
> - ../configure --extra-cflags='-Wno-error=deprecated-declarations'
> --enable-werror --cc=clang || { cat config.log; exit 1; }
> - gmake -j$(sysctl -n hw.ncpu)
> - - gmake check
> + - gmake check V=1
>
> windows_msys2_task:
> windows_container:
--
Alex Bennée
next prev parent reply other threads:[~2020-10-07 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 14:01 [PATCH] cirrus: use V=1 when running tests on FreeBSD and macOS Paolo Bonzini
2020-10-07 14:59 ` Alex Bennée [this message]
2020-10-07 15:10 ` Philippe Mathieu-Daudé
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=87o8leytcg.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--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).