From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: gitlab shared runner time expired
Date: Fri, 19 May 2023 09:49:51 +0100 [thread overview]
Message-ID: <ZGc4L82oE+7nYVFH@redhat.com> (raw)
In-Reply-To: <58b8067d-3136-94ed-f53e-2ccd0feb8c75@linaro.org>
On Thu, May 18, 2023 at 12:26:33PM -0700, Richard Henderson wrote:
> So, here we are again, out of runner time with 13 days left in the month.
>
> Did we come to any resolution since last time? Holding development for that
> long just isn't right, so I'll continue processing the hard way -- testing
> on private runners and local build machines.
There's nothing we need todo, as the jobs are automatically landing on
Eldon's private runner AFAIK. We'll see the scary message about exhausting
all minutes on every job page, but aside from that, everything should
continue working as normal.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-05-19 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 19:26 gitlab shared runner time expired Richard Henderson
2023-05-19 0:41 ` Eldon Stegall
2023-05-19 15:39 ` Richard Henderson
2023-05-19 7:58 ` Mark Cave-Ayland
2023-05-19 8:35 ` Paolo Bonzini
2023-05-19 8:47 ` Camilla Conte
2023-05-19 8:49 ` Daniel P. Berrangé [this message]
2023-05-19 9:18 ` Peter Maydell
2023-05-19 13:30 ` Richard Henderson
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=ZGc4L82oE+7nYVFH@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).