From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
"Emilio G . Cota" <cota@braap.org>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] tests: Disable qht-bench parallel test when using gprof
Date: Thu, 10 Jan 2019 16:25:17 +0000 [thread overview]
Message-ID: <87woncv5si.fsf@linaro.org> (raw)
In-Reply-To: <20190103150951.17592-3-philmd@redhat.com>
Philippe Mathieu-Daudé <philmd@redhat.com> writes:
> This test is failing on the Travis CI [*] since some time now,
> disable it until it get fixed.
>
> [*] https://travis-ci.org/qemu/qemu/builds/474821674
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> v2: Use CONFIG_GPROF via config_host_mak (check-unit isn't target)
> ---
> configure | 1 +
> tests/Makefile.include | 3 ++-
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index fa5c079f98..69a125814d 100755
> --- a/configure
> +++ b/configure
> @@ -7470,6 +7470,7 @@ alpha)
> esac
>
> if test "$gprof" = "yes" ; then
> + echo "CONFIG_GPROF=y" >> $config_host_mak
> echo "TARGET_GPROF=y" >> $config_target_mak
> if test "$target_linux_user" = "yes" ; then
> cflags="-p $cflags"
> diff --git a/tests/Makefile.include b/tests/Makefile.include
> index 3f5a1d0c30..b8f91fdd97 100644
> --- a/tests/Makefile.include
> +++ b/tests/Makefile.include
> @@ -88,7 +88,8 @@ check-unit-y += tests/test-rcu-simpleq$(EXESUF)
> check-unit-y += tests/test-rcu-tailq$(EXESUF)
> check-unit-y += tests/test-qdist$(EXESUF)
> check-unit-y += tests/test-qht$(EXESUF)
> -check-unit-y += tests/test-qht-par$(EXESUF)
> +# FIXME: {test-qht-par + gprof} often break on Travis CI
> +check-unit-$(call lnot,$(CONFIG_GPROF)) +=
> tests/test-qht-par$(EXESUF)
I got confused between test-qht-par and qht-bench. However we already
have this in the test case:
if (g_test_quick()) {
g_test_add_func("/qht/parallel/2threads-0%updates-1s", test_2th0u1s);
g_test_add_func("/qht/parallel/2threads-20%updates-1s", test_2th20u1s);
} else {
g_test_add_func("/qht/parallel/2threads-0%updates-5s", test_2th0u5s);
g_test_add_func("/qht/parallel/2threads-20%updates-5s", test_2th20u5s);
}
So maybe we should be asking why it isn't limiting itself to 1s?
> check-unit-y += tests/test-bitops$(EXESUF)
> check-unit-y += tests/test-bitcnt$(EXESUF)
> check-unit-y += tests/test-qdev-global-props$(EXESUF)
--
Alex Bennée
next prev parent reply other threads:[~2019-01-10 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 15:09 [Qemu-devel] [PATCH v2 0/2] buildsys: Disable qht-bench parallel test when using gprof Philippe Mathieu-Daudé
2019-01-03 15:09 ` [Qemu-devel] [PATCH v2 1/2] configure: Let the TARGET_GPROF var use the regular 'y' for Yes Philippe Mathieu-Daudé
2019-01-03 15:09 ` [Qemu-devel] [PATCH v2 2/2] tests: Disable qht-bench parallel test when using gprof Philippe Mathieu-Daudé
2019-01-10 16:25 ` Alex Bennée [this message]
2019-01-10 19:43 ` Eduardo Habkost
2019-01-03 23:12 ` [Qemu-devel] [PATCH v2 0/2] buildsys: " 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=87woncv5si.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.