git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] ci(dockerized): reduce the PID limit for private repositories

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 1, 2026, 16:54 UTC
Message-ID
<xmqq5x2yps4c.fsf@gitster.g>
In-Reply-To
<pull.2164.git.1782889484346.gitgitgadget@gmail.com>

"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?

And that fix turns constant failures into success (albeit the tests run very slowly, which is a separate topic that you discuss next).

Show 14 quoted lines
> But that's not
> the only difference: The jobs seem to take a lot longer in these
> containers than, say, in the containers made available to
> https://github.com/git/git.
>
> When forcing a PID limit of 64k in that private repository, the jobs
> completed successfully, but they also took a lot longer, between 2x to
> 2.5x longer, i.e. painfully much longer. Reducing the PID limit to 16k,
> the CI jobs still passed, but took an equally long amount of time.
> Reducing the PID limit to 8k caused the errors to reappear.
> ...
> It does not look as if the PID limit is the reason for the longer
> runtime, seeing as the 64k vs 16k timings deviate no more than as is
> usual with GitHub workflows. So let's go for 16k.

So 8k is too low to make them pass, just like the default setting (whatever it is), but 16k is sufficient, so this patch settles at that number, which makes sense.

Show 17 quoted lines
> diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> index cf341d74db..85cfedf5b0 100644
> --- a/.github/workflows/main.yml
> +++ b/.github/workflows/main.yml
> @@ -420,7 +420,9 @@ jobs:
>        CI_JOB_IMAGE: ${{matrix.vector.image}}
>        CUSTOM_PATH: /custom
>      runs-on: ubuntu-latest
> -    container: ${{matrix.vector.image}}
> +    container:
> +      image: ${{ matrix.vector.image }}
> +      options: ${{ github.repository_visibility == 'private' && '--pids-limit 16384 --ulimit nproc=16384:16384 --ulimit nofile=32768:32768' || '' }}
>      steps:
>      - name: prepare libc6 for actions
>        if: matrix.vector.jobname == 'linux32'
>
> base-commit: e9019fcafe0040228b8631c30f97ae1adb61bcdc
Previous: Johannes Schindelin via GitGitGadgetNext: Johannes Schindelin
Message 2 of 5 in “ci(dockerized): reduce the PID limit for private repositories”
  1. ci(dockerized): reduce the PID limit for private repositoriesJohannes Schindelin via GitGitGadget, Jul 1, 2026
  2. Junio C HamanoJul 1, 2026
  3. Johannes SchindelinJul 4, 2026
  4. ci(dockerized): raise the PID limit for private repositoriesJohannes Schindelin via GitGitGadget, Jul 4, 2026
  5. Junio C HamanoJul 5, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.