On 5/18/23 17:41, Eldon Stegall wrote:
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 contin
On 5/19/23 02:18, Peter Maydell wrote:
On Thu, 18 May 2023 at 20:27, Richard Henderson
wrote:
So, here we are again, out of runner time with 13 days left in the month.
This is quite early -- have you been processing pull requests
strictly one at a time, or in (small) batches ?
Mostly one a
On Thu, 18 May 2023 at 20:27, Richard Henderson
wrote:
>
> So, here we are again, out of runner time with 13 days left in the month.
This is quite early -- have you been processing pull requests
strictly one at a time, or in (small) batches ?
-- PMM
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 -- testi
Hi!
On Fri, May 19, 2023 at 9:35 AM Paolo Bonzini wrote:
> You should be able to run pipelines almost as usual, just with
>
> git push -o ci.variable=RUNNER_TAG=k8s ...
>
> Camilla, please confirm that this is correct.
Looks good.
On 5/18/23 21:26, 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 lo
On 18/05/2023 20:26, 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 an
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 -- t
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.
r~
