From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] ci(dockerized): reduce the PID limit for private repositories
Date: Sat, 4 Jul 2026 10:46:56 +0200 (CEST) [thread overview]
Message-ID: <c2986e77-1622-a148-98a9-2f7ce6717827@gmx.de> (raw)
In-Reply-To: <xmqq5x2yps4c.fsf@gitster.g>
Hi Junio,
On Wed, 1 Jul 2026, Junio C Hamano wrote:
> "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
> writes:
>
> > The underlying reason seems to be a substantial difference in the hosted
> > runners that execute these Dockerized jobs: forcing the PID limit of the
> > container to a high number lets the jobs pass, even when running the
> > complete matrix of all 13 Dockerized jobs concurrently.
>
> Is the "reduce" in the title accurate? The above description tells
> me that what you did was to "raise" the PID limit (i.e., forcing the
> PID limit to a high number), presumably because the default PID
> limit is way too low for the tests to pass?
You are right; The subject is wrong. The patch raises the limit from
the hosted-runner default to 16384. The subject is a left-over from a
hypothesis that my experiments refuted.
v2 will retitle to "ci(dockerized): raise the PID limit for private
repositories". No code change: 16k remains the sweet spot between the
failures we saw at 8k and the slow runs at 64k.
Ciao,
Johannes
next prev parent reply other threads:[~2026-07-04 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 7:04 [PATCH] ci(dockerized): reduce the PID limit for private repositories Johannes Schindelin via GitGitGadget
2026-07-01 16:54 ` Junio C Hamano
2026-07-04 8:46 ` Johannes Schindelin [this message]
2026-07-04 8:52 ` [PATCH v2] ci(dockerized): raise " Johannes Schindelin via GitGitGadget
2026-07-05 5:28 ` Junio C Hamano
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=c2986e77-1622-a148-98a9-2f7ce6717827@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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