Re: [PATCH v2 2/2] ci: align job counts across CI providers

From: Patrick Steinhardt <ps@pks.im>
Date: Sep 28, 2026, 06:36 UTC
Message-ID: <aroK7KcRabARSqd8@pks.im>
In-Reply-To: <20260925-ci-large-test-resources-v2-2-f632cf319756@gmail.com>

On Fri, Sep 25, 2026 at 12:35:39PM -0400, Tamir Duberstein wrote:

> GitHub Actions sets JOBS to ten regardless of runner size, while
> GitLab CI uses the detected CPU count. Use the CPU count for Make and
> prove on both providers, selecting JOBS after the operating system
> is identified.

Again, it should be noted here what the effect of this is. In other words, does GitHub slow down as a result? You already showed numbers during the discussion on v1 of this series, and these numbers should probably be included in this message, too.

> Use nproc on Linux and NUMBER_OF_PROCESSORS on Windows. On macOS, use
> sysctl to avoid requiring nproc before the dependency installer has run;
> GitHub macOS images need not provide GNU coreutils.

Huh... "need not" feels somewhat weird as phrasing. I guess it's rather "does not", and consequently we have to adapt? I think instead of describing what you do, I'd directly pinpoint what matters:

  Note that we continue to use the same logic to detect the number of
  processors on both Linux and Windows. But on macOS, we cannot continue
  to use nproc(1) because the image used by GitHub does not provide that
  tool. Use sysctl instead, which is available on both GitLab and
  GitHub.

Thanks!

Patrick