From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: [PATCH 3/5] ci: make test slicing consistent across Meson/Make
Date: Tue, 10 Feb 2026 17:54:01 -0500 [thread overview]
Message-ID: <20260210225401.GA1837188@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqa4xgxn2m.fsf@gitster.g>
On Tue, Feb 10, 2026 at 02:15:13PM -0800, Junio C Hamano wrote:
> > diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> > index 2b175dc5c6..1b7a16e1f1 100644
> > --- a/.github/workflows/main.yml
> > +++ b/.github/workflows/main.yml
> > @@ -298,7 +298,7 @@ jobs:
> > path: build
> > - name: Test
> > shell: pwsh
> > - run: ci/run-test-slice-meson.sh build ${{matrix.nr}} 10
> > + run: ci/run-test-slice-meson.sh build ${{matrix.nr + 1}} 10
> > - name: print test failures
> > if: failure() && env.FAILED_TEST_ARTIFACTS != ''
> > shell: bash
>
> Have we successfully run this one?
>
> I am getting
>
> Invalid workflow file: .github/workflows/main.yml#L1
> (Line: 153, Col: 12): Unexpected symbol: '+'. Located at position 11
> within expression: matrix.nr + 1, (Line: 301, Col: 12): Unexpected
> symbol: '+'. Located at position 11 within expression: matrix.nr + 1
>
> https://github.com/orgs/community/discussions/25386 is a 6-year old
> discussion so things may have changed quite a lot, but at least back
> then the claim was
>
> Github actions doesn’t support math operations in expressions
> inside ${{ }}. You could add up these two numbers in bash script and
> then use set-env command to give its value to an environment
> variable ...
>
> though.
Right, that's why we used pwsh syntax to do it before, in d3d6493dcf
(ci: use Meson's new `--slice` option, 2025-07-09).
That went away in 17bd1108ea (ci(windows-meson-test): handle options and
output like other test jobs, 2025-11-18), because the "+1" was added
into the script itself there. It looks like the patch under discussion
removes the +1 from the script, so we'd need to go back to the pwsh
syntax.
-Peff
next prev parent reply other threads:[~2026-02-10 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 16:56 [PATCH 0/5] Some assorted fixes for GitLab CI Patrick Steinhardt
2026-02-09 16:56 ` [PATCH 1/5] ci: handle failures of test-slice helper Patrick Steinhardt
2026-02-09 16:56 ` [PATCH 2/5] ci: don't skip smallest test slice in GitLab Patrick Steinhardt
2026-02-09 18:07 ` Justin Tobler
2026-02-09 16:56 ` [PATCH 3/5] ci: make test slicing consistent across Meson/Make Patrick Steinhardt
2026-02-09 18:19 ` Justin Tobler
2026-02-10 5:34 ` Patrick Steinhardt
2026-02-10 22:15 ` Junio C Hamano
2026-02-10 22:54 ` Jeff King [this message]
2026-02-11 6:33 ` Patrick Steinhardt
2026-02-09 16:56 ` [PATCH 4/5] gitlab-ci: use "run-test-slice-meson.sh" Patrick Steinhardt
2026-02-09 16:56 ` [PATCH 5/5] gitlab-ci: handle failed tests on MSVC+Meson job Patrick Steinhardt
2026-02-09 18:33 ` Justin Tobler
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=20260210225401.GA1837188@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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