From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: [PATCH 0/6] Shorten the runtime of some gitlab-CI shared runner jobs
Date: Mon, 30 Jan 2023 11:44:40 +0100 [thread overview]
Message-ID: <20230130104446.1286773-1-thuth@redhat.com> (raw)
We're currently facing the problem that the gitlab-CI jobs for the
shared runners take too much of the limited CI minutes on gitlab.com.
Here are now some patches that optimize some of the jobs a little bit
to take less runtime. We slightly lose some test coverage by some of
these changes (e.g. by dropping ppc-softmmu from a Clang-based test
and only continue testing ppc64-softmmu with Clang in another job),
but that should still be much better than running out of CI minutes
after 3/4 of a month.
Thomas Huth (6):
gitlab-ci.d/buildtest: Remove ppc-softmmu from the clang-system job
gitlab-ci.d/buildtest: Remove aarch64-softmmu from the
build-system-ubuntu job
tests/qtest/display-vga-test: Add proper checks if a device is
available
gitlab-ci.d/buildtest: Merge the --without-default-* jobs
gitlab-ci.d/buildtest: Merge the two gprof-gcov jobs
gitlab-ci.d/buildtest: Disintegrate the build-coroutine-sigaltstack
job
tests/qtest/display-vga-test.c | 65 +++++++++++++---------------------
.gitlab-ci.d/buildtest.yml | 51 ++++++--------------------
.gitlab-ci.d/crossbuilds.yml | 2 +-
3 files changed, 37 insertions(+), 81 deletions(-)
--
2.31.1
next reply other threads:[~2023-01-30 10:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 10:44 Thomas Huth [this message]
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
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=20230130104446.1286773-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=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 \
/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).