From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: "Alexandre Iooss" <erdnaxe@crans.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
qemu-arm@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Xu" <peterx@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Mahmoud Mandour" <ma.mandourr@gmail.com>
Subject: Re: [PATCH 2/9] gitlab: disable debug info on CI builds
Date: Mon, 28 Apr 2025 16:01:57 +0200 [thread overview]
Message-ID: <294fd9b9-6880-477f-a2b4-773f1e5274c8@redhat.com> (raw)
In-Reply-To: <20250428125918.449346-3-alex.bennee@linaro.org>
On 28/04/2025 14.59, Alex Bennée wrote:
> Our default build enables debug info which adds hugely to the size of
> the builds as well as the size of cached objects. Disable debug info
> across the board to save space and reduce pressure on the CI system.
> We still have a number of builds which explicitly enable debug and
> related extra asserts like --enable-debug-tcg.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> .gitlab-ci.d/buildtest-template.yml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.gitlab-ci.d/buildtest-template.yml b/.gitlab-ci.d/buildtest-template.yml
> index d4f145fdb5..d9e69c3237 100644
> --- a/.gitlab-ci.d/buildtest-template.yml
> +++ b/.gitlab-ci.d/buildtest-template.yml
> @@ -24,6 +24,7 @@
> - ccache --zero-stats
> - section_start configure "Running configure"
> - ../configure --enable-werror --disable-docs --enable-fdt=system
> + --disable-debug-info
Do we have any jobs that might show stack traces in the console output ?
build-oss-fuzz comes to my mind, but that uses a separate script, so we
should be fine there?
So assuming there are no other jobs around that might need it:
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2025-04-28 14:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 12:59 [PATCH 0/9] Maintainer updates for May (testing, plugins, virtio-gpu) Alex Bennée
2025-04-28 12:59 ` [PATCH 1/9] tests/docker: expose $HOME/.cache as docker volume Alex Bennée
2025-04-28 14:00 ` Thomas Huth
2025-04-28 12:59 ` [PATCH 2/9] gitlab: disable debug info on CI builds Alex Bennée
2025-04-28 14:01 ` Thomas Huth [this message]
2025-04-28 14:20 ` Peter Maydell
2025-05-02 7:45 ` Manos Pitsidianakis
2025-04-28 12:59 ` [PATCH 3/9] tests/tcg: make aarch64 boot.S handle different starting modes Alex Bennée
2025-05-02 7:54 ` Manos Pitsidianakis
2025-04-28 12:59 ` [PATCH 4/9] contrib/plugins: add a scaling factor to the ips arg Alex Bennée
2025-04-28 16:56 ` Pierrick Bouvier
2025-04-28 12:59 ` [PATCH 5/9] contrib/plugins: allow setting of instructions per quantum Alex Bennée
2025-04-28 16:49 ` Pierrick Bouvier
2025-04-28 12:59 ` [PATCH 6/9] MAINTAINERS: add myself to virtio-gpu for Odd Fixes Alex Bennée
2025-04-28 13:52 ` Thomas Huth
2025-04-29 18:56 ` Dmitry Osipenko
2025-05-04 7:20 ` Akihiko Odaki
2025-05-05 16:07 ` Dmitry Osipenko
2025-05-06 10:13 ` Alex Bennée
2025-04-28 12:59 ` [PATCH 7/9] hw/display: re-arrange memory region tracking Alex Bennée
2025-04-28 12:59 ` [PATCH 8/9] virtio-gpu: fix hang under TCG when unmapping blob Alex Bennée
2025-04-29 18:48 ` Dmitry Osipenko
2025-04-29 21:19 ` Alex Bennée
2025-04-29 21:26 ` Dmitry Osipenko
2025-04-30 10:24 ` Alex Bennée
2025-04-30 20:42 ` Dmitry Osipenko
2025-05-04 8:19 ` Akihiko Odaki
2025-05-06 10:12 ` Alex Bennée
2025-05-08 11:44 ` Akihiko Odaki
2025-04-28 12:59 ` [PATCH 9/9] virtio-gpu: refactor async blob unmapping Alex Bennée
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=294fd9b9-6880-477f-a2b4-773f1e5274c8@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=david@redhat.com \
--cc=erdnaxe@crans.org \
--cc=ma.mandourr@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).