From: "Alex Bennée" <alex.bennee@linaro.org>
To: Eldon Stegall <eldon-qemu@eldondev.com>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Ben Dooks" <qemu@ben.fluff.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: out of CI pipeline minutes again
Date: Wed, 01 Mar 2023 09:53:51 +0000 [thread overview]
Message-ID: <875ybkeqvt.fsf@linaro.org> (raw)
In-Reply-To: <Y/7ZzH/X5eb3vhPG@invalid>
Eldon Stegall <eldon-qemu@eldondev.com> writes:
> On Mon, Feb 27, 2023 at 12:43:55PM -0500, Stefan Hajnoczi wrote:
>> - Personally, I don't think this should exclude other efforts like
>> Eldon's. We can always add more private runners!
>
> Hi!
> Thanks so much to Alex, Thomas, Gerd, et al for the pointers.
>
> Although the month has passed and presumably gitlab credits have
> replenished, I am interested in continuing my efforts to replicate the
> shared runner capabilities. After some tinkering I was able to utilise
> Gerd's stateless runner strategy with a few changes, and had a number of
> tests pass in a pipeline on my repo:
>
> https://gitlab.com/eldondev/qemu/-/pipelines/791573670
Looking good. Eyeballing the run times they seem to be faster as well. I
assume the runner is less loaded than the shared gitlab ones?
> Looking at the failures, it seems that some may already be addressed in
> patchsets, and some may be attributable to things like open file handle
> count, which would be useful to configure directly on the d-in-d
> runners, so I will investigate those after integrating the changes from
> the past couple of days.
>
> I have been reading through Alex's patchsets to lower CI time in the
> hopes that I might be able to contribute something there from my
> learnings on these pipelines. If there is an intent to switch to the
> kubernetes gitlab executor, I have worked with kubernetes a number of
> times in the past, and I can trial that as well.
I've dropped that patch for now but I might revisit once the current
testing/next is done.
> Even with the possibility of turning on Azure and avoiding these monthly
> crunches, maybe I can provide some help improving the turnaround time of
> some of the jobs themselves, once I polish off greening the remaining
> failures on my fork.
>
> Forgive me if I knock around a bit here while I figure out how to be
> useful.
No problem, thanks for taking the time to look into it.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-03-01 9:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 12:56 out of CI pipeline minutes again Peter Maydell
2023-02-23 13:46 ` Thomas Huth
2023-02-23 14:14 ` Daniel P. Berrangé
2023-02-23 14:15 ` Warner Losh
2023-02-23 15:00 ` Daniel P. Berrangé
2023-02-23 15:28 ` Ben Dooks
2023-02-23 15:33 ` Daniel P. Berrangé
2023-02-23 22:11 ` Eldon Stegall
2023-02-24 9:16 ` Gerd Hoffmann
2023-02-24 14:07 ` Alex Bennée
2023-02-27 16:59 ` Daniel P. Berrangé
2023-02-27 17:43 ` Stefan Hajnoczi
2023-03-01 4:51 ` Eldon Stegall
2023-03-01 9:53 ` Alex Bennée [this message]
2023-03-21 16:40 ` Daniel P. Berrangé
2023-03-23 5:53 ` Eldon Stegall
2023-03-23 9:05 ` Alex Bennée
2023-03-23 9:18 ` Paolo Bonzini
2023-02-24 9:54 ` Paolo Bonzini
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=875ybkeqvt.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=eldon-qemu@eldondev.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu@ben.fluff.org \
--cc=stefanha@gmail.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.