AFAICT they wait for an open runner. That is the behavior we were observing
last week.
I don't know if there are any queue time or queue length limits around
that. I expect if there are they wouldn't really be relevant to our normal
use; e.g. they'd be GitHub protecting itself against user errors or malice.
On Tue, Oct 17, 2023 at 8:43 AM Martin Stefanko <mstefank(a)redhat.com> wrote:
Just out of curiosity, I can't find this in the documentation.
What
happens if you hit more than 20 concurrent jobs? They are just not
started/listed, do they wait for when they could run within 20 concurrent
jobs, or maybe they are rejected/canceled and GH doesn't track the restart?
Cheers,
Martin Stefanko
Principal Software Engineer
Middleware Runtimes Sustaining Engineering Team
Red Hat
On Thu, Oct 12, 2023 at 9:58 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
> Before anyone adds any more github actions to projects in the 'wildfly'
> github org, please discuss here or in zulip.
>
> GH actions jobs have been essentially free for a long time from our naive
> POV, but we do have a max of 20 concurrent jobs across the whole github
> org, which we're starting to hit
>
> So we should discuss new ones to make sure they are a good use of our
> limit.
> Best regards,
> Brian
>
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> Privacy Statement:
https://www.redhat.com/en/about/privacy-policy
> List Archives:
>
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
>
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His