From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: [PATCH 5/6] gitlab-ci.d/buildtest: Merge the two gprof-gcov jobs
Date: Mon, 30 Jan 2023 17:42:32 +0000 [thread overview]
Message-ID: <87tu076hpq.fsf@linaro.org> (raw)
In-Reply-To: <20230130104446.1286773-6-thuth@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> There is only one job depending on the build-gprof-gcov job, so
> there is no real need for keeping this separate. It likely only
> has been split since the complete runtime is more than 60 minutes,
> but that can be better handled with a proper timeout setting instead.
> By merging the two jobs, we safe some precious CI minutes for starting
> a new container for the second job each time.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> .gitlab-ci.d/buildtest.yml | 15 ++-------------
> 1 file changed, 2 insertions(+), 13 deletions(-)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index 86f9c37a07..91c7467a66 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -468,26 +468,15 @@ tsan-build:
> MAKE_CHECK_ARGS: bench V=1
>
> # gprof/gcov are GCC features
> -build-gprof-gcov:
> +gprof-gcov:
> extends: .native_build_job_template
> needs:
> job: amd64-ubuntu2004-container
> + timeout: 80m
> variables:
> IMAGE: ubuntu2004
> CONFIGURE_ARGS: --enable-gprof --enable-gcov
> TARGETS: aarch64-softmmu ppc64-softmmu s390x-softmmu x86_64-softmmu
> - artifacts:
> - expire_in: 1 days
> - paths:
> - - build
> -
> -check-gprof-gcov:
> - extends: .native_test_job_template
> - needs:
> - - job: build-gprof-gcov
> - artifacts: true
> - variables:
> - IMAGE: ubuntu2004
> MAKE_CHECK_ARGS: check
> after_script:
> - cd build
I'm tempted to deprecate gprof altogether as I find it hard to believe
anyone uses it when perf tools give you a much clearer indication of
where the bottlenecks are in "real world" environments.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-01-30 17:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 10:44 [PATCH 0/6] Shorten the runtime of some gitlab-CI shared runner jobs Thomas Huth
2023-01-30 10:44 ` [PATCH 1/6] gitlab-ci.d/buildtest: Remove ppc-softmmu from the clang-system job Thomas Huth
2023-01-30 22:37 ` Philippe Mathieu-Daudé
2023-01-30 10:44 ` [PATCH 2/6] gitlab-ci.d/buildtest: Remove aarch64-softmmu from the build-system-ubuntu job Thomas Huth
2023-01-30 10:44 ` [PATCH 3/6] tests/qtest/display-vga-test: Add proper checks if a device is available Thomas Huth
2023-01-30 21:13 ` Richard Henderson
2023-01-30 10:44 ` [PATCH 4/6] gitlab-ci.d/buildtest: Merge the --without-default-* jobs Thomas Huth
2023-01-30 13:28 ` Fabiano Rosas
2023-01-31 8:02 ` Thomas Huth
2023-01-30 17:45 ` Alex Bennée
2023-01-30 22:43 ` Philippe Mathieu-Daudé
2023-01-30 10:44 ` [PATCH 5/6] gitlab-ci.d/buildtest: Merge the two gprof-gcov jobs Thomas Huth
2023-01-30 17:42 ` Alex Bennée [this message]
2023-01-31 7:53 ` Thomas Huth
2023-01-30 10:44 ` [PATCH 6/6] gitlab-ci.d/buildtest: Disintegrate the build-coroutine-sigaltstack job Thomas Huth
2023-01-30 10:58 ` Daniel P. Berrangé
2023-01-30 12:05 ` Thomas Huth
2023-02-03 11:23 ` Thomas Huth
2023-02-03 12:08 ` Kevin Wolf
2023-02-03 15:44 ` Thomas Huth
2023-02-03 15:47 ` Peter Maydell
2023-02-03 21:14 ` Juan Quintela
2023-02-04 10:23 ` Peter Maydell
2023-02-06 9:36 ` Juan Quintela
2023-02-06 7:44 ` Thomas Huth
2023-02-06 8:46 ` Juan Quintela
2023-02-06 10:47 ` Peter Maydell
2023-02-03 21:10 ` Juan Quintela
2023-02-02 11:30 ` [PATCH 0/6] Shorten the runtime of some gitlab-CI shared runner jobs 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=87tu076hpq.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.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 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.